Date: Tue, 25 Apr 2006 10:22:54 +0900 From: gnn@freebsd.org To: Kirk McKusick <mckusick@chez.mckusick.com> Cc: arch@freebsd.org Subject: Re: Linus Torvalds on FreeBSD's Use of Copy-on-write Message-ID: <m2fyk24ff5.wl%gnn@neville-neil.com> In-Reply-To: <200604240633.k3O6XUJ0042841@chez.mckusick.com> References: <200604240633.k3O6XUJ0042841@chez.mckusick.com>
next in thread | previous in thread | raw e-mail | index | archive | help
At Sun, 23 Apr 2006 23:33:30 -0700, Kirk McKusick wrote: > > Anyone working on zero-copy sockets care to respond to this? > > http://developers.slashdot.org/developers/06/04/21/1536213.shtml > > Linus Torvalds made reference to some possible future extensions. > This included vmsplice(), a system call since implemented by Jens > Axboe "to basically do a 'write to the buffer', but using the > reference counting and VM traversal to actually fill the buffer." > Reviewing the implications of using such a system call lead to a > comparison with FreeBSD's ZERO_COPY_SOCKET which uses COW (copy on > write). > To be honest, what all this has made me think of is that we should have a "big board" of unsolved problems we'd like to look at. This certainly deserves a place, as it's an interesting question. As scientists and engineers we should be interested in such things, even if the original statement was poorly worded. Perhaps on a FreeBSD Feature Wiki? We could even propose a benchmark as a SoC project. Later, George
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?m2fyk24ff5.wl%gnn>