Date: Wed, 5 Nov 2003 02:29:47 -0600 (CST) From: Mike Silbersack <silby@silby.com> To: Vivek Pai <vivek@CS.Princeton.EDU> Cc: Alan Cox <alc@cs.rice.edu> Subject: Re: Update: Debox sendfile modifications Message-ID: <20031105022737.J1370@odysseus.silby.com> In-Reply-To: <3FA897E7.5020103@cs.princeton.edu> References: <1066789354.21430.39.camel@boxster.onthenet.com.au> <20031022082953.GA69506@rot13.obsecurity.org> <1066816287.25609.34.camel@boxster.onthenet.com.au> <20031022095754.GA70026@rot13.obsecurity.org> <xzpk76sc425.fsf@dwp.des.no> <1067183332.3f9bece4c0cf4@webmail.cs.princeton.edu> <3FA2C43E.3030204@cs.princeton.edu> <3FA7EF77.5010808@cs.princeton.edu> <20031104221455.I9997@odysseus.silby.com> <3FA897E7.5020103@cs.princeton.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 5 Nov 2003, Vivek Pai wrote: > If you were to have sendfile issue the disk reads, how would you signal > completion? I guess one approach is to make the socket buffer appear to > have no space while the sendfile-initiated read is in progress, but > it seems to me that such an approach would be considered too ugly. It > would cause the least modification to applications, because otherwise > apps need to disable interest on the socket having space, and re-enable > it after getting notified that the sendfile-initiated read (and > transfer) completed. Am I missing something? > > -Vivek I'm not quite certain how I would do it yet. At this point in time I'm just brainstorming. I have some other things I'd like to work on in the next few weeks, I'll sit down and think about this more in late November / early December if I'm still in the right mindset. Mike "Silby" Silbersack
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20031105022737.J1370>