Re: Status of AIO

[Phillip Susi <psusi@cfl.rr.com>]

David S. Miller wrote:
> The whole idea is to figure out what socket gets the packet
> without going through the IP and TCP stack at all, in the
> hardware interrupt handler, using a tiny classifier that's
> very fast and can be implemented in hardware.
> 

AFAIK, "going through the IP and TCP stack" just means passing a quick 
packet classifier to locate the corresponding socket.  It would be nice 
to be able to possibly offload that to the hardware, but you don't need 
to throw out the baby ( tcp/ip stack ) with the bathwater to get there.

Maybe some sort of interface could be constructed to allow the higher 
layers to pass down some sort of ASL type byte code classifier to the 
NIC driver, which could either call it via the kernel software ASL 
interpreter, or convert it to firmware code to load into the hardware.

> Please wrap your brain around the idea a little longer than
> the 15 or so minutes you have thus far... thanks.
> 

I've had my brain wrapped around these sort of networking problems for 
over 10 years now, so I think I have a fair handle on things.  Certainly 
enough to carry on a discussion about it.

>> Yes, we can and should have a 6 times speed up, but as I've explained 
>> above, NT has had that for 10 years without having to push TCP into user 
>> space.
> 
> That's complete BS.

Error, does not compute.

Your holier than thou attitude does not a healthy discussion make.  I 
explained the methods that have been in use on NT to achieve a 6 fold 
decrease in cpu utilization for bulk network IO, and how it can be 
applied to the Linux kernel without radical changes.  If you don't 
understand it, then ask sensible questions, not just cry "That's 
complete BS!"

We already have O_DIRECT aio for disk drives that can do zero copy, 
there's no reason not to apply that to the network stack as well.