From mboxrd@z Thu Jan 1 00:00:00 1970 From: erik quanstrom Date: Mon, 15 Oct 2018 17:09:43 -0700 To: 9fans@9fans.net Message-ID: <59b9f4f7b09c690484ff47656f2bb542@mule.quanstro.net> In-Reply-To: References: <7aa20c07322147e6@orthanc.ca> <20181011230430.8ec148a3cb2a4d95180a4ad2@eigenstate.org> <4A1686D0-C80C-417F-A3D6-3F9EA327D35F@lsub.org> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Subject: Re: [9fans] zero copy & 9p (was Re: PDP11 (Was: Re: what heavy negativity!) Topicbox-Message-UUID: ede2eecc-ead9-11e9-9d60-3106f5b1d025 > It's useful internally in protocol implementation, specifically to avoid > copying in transport protocols (for later retransmission), and the > modifications aren't vast. > A few changes were trickier, often because of small bugs in the original > code. icmp does some odd things i think. that makes sense. likewise, if it were essentially free to add file systems in the i/o path, from user space, one could build micro file systems that took care of small details without incuring much cost. ramfs is enough of a file system if you have other programs to do other things like dump. > I'll see if I wrote up some of it. I think there were manual pages for the > Messages replacing Blocks. that would be great. thanks. > My mcs lock implementation was probably more useful, and I use that in my > copy of the kernel known as 9k indeed. i've seen great performance with mcs in my kernel. - erik