Date: Tue, 23 Oct 2012 11:23:23 -0500 From: Alan Cox <alc@rice.edu> To: Gleb Smirnoff <glebius@FreeBSD.org> Cc: svn-src-head@FreeBSD.org, svn-src-all@FreeBSD.org, src-committers@FreeBSD.org, Andre Oppermann <andre@FreeBSD.org> Subject: Re: svn commit: r241931 - in head/sys: conf kern Message-ID: <5086C47B.9080202@rice.edu> In-Reply-To: <20121023160501.GB70741@FreeBSD.org> References: <201210231419.q9NEJjYH082863@svn.freebsd.org> <20121023144211.GX70741@FreeBSD.org> <5086B24C.9000606@freebsd.org> <20121023160501.GB70741@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 10/23/2012 11:05, Gleb Smirnoff wrote: > On Tue, Oct 23, 2012 at 05:05:48PM +0200, Andre Oppermann wrote: > A> There shouldn't be any users. Zero copy send is broken and > A> responsible for random kernel crashes. Zero copy receive isn't > A> supported by any modern driver. Both are useless to dangerous. > A> > A> The main problem with ZERO_COPY_SOCKETS was that it sounded great > A> and who wouldn't want to have zero copy sockets? Unfortunately > A> it doesn't work that way. > > Okay, it appeared that there are users, even on current@ mailing > list during couple of hours of exposition. In my experience, that is because they are reporting a crash. > Can we keep the old option as compatibility? > >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5086C47B.9080202>