On Sunday 06 February 2005 12:03, Stephen wrote: > AOLserver doesn't do scatter/gather IO. > Hmm, well in nssock.c, there is this note: * SockProc -- * * Socket driver callback proc. This driver attempts efficient * scatter/gatter I/O if requested and only blocks for the * driver configured time once if no bytes are available. *
SockSend uses sendmsg, which sends multiple buffers in one call. SockRecv uses recvmsg, which receives input into multiple buffers. How else does AOLserver read/write that avoids scatter/gather? > Read-ahead refers to the driver thread accepting new connections and > reading data from the socket before passing it to a connection thread > to run. This beneficially prevents precious connection threads from > blocking for data as it dribbles in over a 14k modem. > > Read-ahead is more aggressive in 4.0 because it reads the entire > request, not just the request line and headers as was the case in 3.x. > That's why the new upload limit of 2MB which caught a lot of people I think we are referring to the same thing here. The socket driver uses scatter/gather, but this is transparent to the application. tom jackson -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]> with the body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: field of your email blank.
