From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] zero copy & 9p (was Re: PDP11 (Was: Re: what heavy negativity!)
Date: Mon, 15 Oct 2018 17:09:43 -0700 [thread overview]
Message-ID: <59b9f4f7b09c690484ff47656f2bb542@mule.quanstro.net> (raw)
In-Reply-To: <CAOw7k5ijD9K2=DMJQ7orO5o=Kzw5KGie-nPfn+Sgk3z8PXdJtA@mail.gmail.com>
> 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
next prev parent reply other threads:[~2018-10-16 0:09 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-10 17:34 [9fans] " cinap_lenrek
2018-10-10 21:54 ` Steven Stallion
2018-10-10 22:26 ` [9fans] zero copy & 9p (was " Bakul Shah
2018-10-10 22:52 ` Steven Stallion
2018-10-11 20:43 ` Lyndon Nerenberg
2018-10-11 22:28 ` hiro
2018-10-12 6:04 ` Ori Bernstein
2018-10-13 18:01 ` Charles Forsyth
2018-10-13 21:11 ` hiro
2018-10-14 5:25 ` FJ Ballesteros
2018-10-14 7:34 ` hiro
2018-10-14 7:38 ` Francisco J Ballesteros
2018-10-14 8:00 ` hiro
2018-10-15 16:48 ` Charles Forsyth
2018-10-15 17:01 ` hiro
2018-10-15 17:29 ` hiro
2018-10-15 23:06 ` Charles Forsyth
2018-10-16 0:09 ` erik quanstrom [this message]
2018-10-17 18:14 ` Charles Forsyth
2018-10-10 22:29 ` [9fans] " Kurt H Maier
2018-10-10 22:55 ` Steven Stallion
2018-10-11 11:19 ` Aram Hăvărneanu
2018-10-11 0:26 ` Skip Tavakkolian
2018-10-11 1:03 ` Steven Stallion
2018-10-14 9:46 ` Ole-Hjalmar Kristensen
2018-10-14 10:37 ` hiro
2018-10-14 17:34 ` Ole-Hjalmar Kristensen
2018-10-14 19:17 ` hiro
2018-10-15 9:29 ` Giacomo Tesio
2018-10-10 23:58 [9fans] zero copy & 9p (was " cinap_lenrek
2018-10-11 0:56 ` Dan Cross
2018-10-11 2:26 ` Steven Stallion
2018-10-11 2:30 ` Bakul Shah
2018-10-11 3:20 ` Steven Stallion
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=59b9f4f7b09c690484ff47656f2bb542@mule.quanstro.net \
--to=quanstro@quanstro.net \
--cc=9fans@9fans.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).