Incorporating I/O driven scheduling into OS Kernel

Question

IronPort developed a high performance file system and an I/O driven scheduler optimized for the asynchronous nature of messaging (hence "Async"OS).

If you wanted to do the same but make it open source, what exactly would need to change?

Answer 1

This is probably mostly marketing - FreeBSD already handles "asynchronous nature of messaging" rather well. They most likely short-circuited some processing in the network stack for their specific purposes, same for the file system.