From: "David Leimbach" <leimy2k@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] kernel development: how not to
Date: Fri, 5 May 2006 08:19:13 -0700 [thread overview]
Message-ID: <3e1162e60605050819g796711aeo345776dd940f3e7f@mail.gmail.com> (raw)
In-Reply-To: <20060505151218.5560223C90F@dexter-peak.quanstro.net>
Is the the vmslice that Linus told BSD people they were a bunch of
retards for not having?
On 5/5/06, erik quanstrom <quanstro@quanstro.net> wrote:
> the linux guys decided to implement system calls
> "splice" and "tee". splice concatinates the pages from
> two files -- the vm equivalent of "cat a b". tee
> is the vm equivalent of its namesake.
>
> http://lwn.net/Articles/181169/#Comments
>
> the best part is the conclusion -- "needs a bit more work".
> ha!
>
> - erik
>
next prev parent reply other threads:[~2006-05-05 15:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-05 15:12 erik quanstrom
2006-05-05 15:19 ` David Leimbach [this message]
2006-05-05 15:41 erik quanstrom
2006-05-08 15:44 ` Dave Lukes
2006-05-08 19:41 erik quanstrom
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=3e1162e60605050819g796711aeo345776dd940f3e7f@mail.gmail.com \
--to=leimy2k@gmail.com \
--cc=9fans@cse.psu.edu \
/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).