On 2/1/06, Andi Kleen <[EMAIL PROTECTED]> wrote: > On Wednesday 01 February 2006 20:37, Jeff Garzik wrote: > > > To have a fully async, zero copy network receive, POSIX read(2) is > > inadequate. > > Agreed, but POSIX aio is adequate. > > > One needs a ring buffer, similar in API to the mmap'd > > packet socket, where you can queue a whole bunch of reads. Van's design > > seems similar to this. > > See lio_listio et.al. > > But I don't think Van's design is supposed to be exposed to user space. > It's just a better way to implement BSD sockets.
Well, for DCCP it seems interesting, look at: http://www.icir.org/kohler/dccp/nsdiabstract.pdf # A Congestion-Controlled Unreliable Datagram API Junwen Lai and Eddie Kohler Describes a potential DCCP API based on a shared-memory packet ring. The API simultaneously achieves kernel-implemented congestion control, high throughput, and late data choice, where the app can change what's sent very late in the process. Shows that congestion-controlled DCCP API can improve the rate of "important" frames delivered, relative to non-congestion-controlled UDP, in some situations. - Arnaldo - To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
