Ulrich Drepper wrote:
What has network I/O to do with O_DIRECT? I'm talking about async network I/O.
O_DIRECT allows for zero copy IO, which saves a boatload of cpu cycles.
For disk IO it is possible to use O_DIRECT without aio, but there is
generally a loss of efficiency doing so. For network IO, O_DIRECT is
not even possible without aio.
By using aio and O_DIRECT for network IO, you can achieve massive
performance and scalability gains.
You said before that the kernel aio interface is not suitable for
sockets. Why not?
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
