From: Rob Pike <robpike@gmail.com>
To: Anthony Martin <ality@pbrane.org>
Cc: TUHS main list <tuhs@minnie.tuhs.org>, Paul Ruizendaal <pnr@planet.nl>
Subject: Re: [TUHS] STREAMS performance
Date: Mon, 13 Apr 2020 13:14:55 +1000 [thread overview]
Message-ID: <CAKzdPgzXtrbLD_te9GNRxOs82rZNh68dG0d_u=w=X9rmWgKmXw@mail.gmail.com> (raw)
In-Reply-To: <20200413030020.GA67784@alice>
Nice to see Egreg again.
-rob
On Mon, Apr 13, 2020 at 1:00 PM Anthony Martin <ality@pbrane.org> wrote:
>
> Rob Pike <robpike@gmail.com> once said:
> > It did? I think a version of streams showed up at some point, and were
> > replaced; of that you are correct. But it certainly didn't begin with
> > anything like streams. It began with a file system mux.
>
> I realize you would probably know better, but ...
>
> I didn't mean that streams was the first thing in Plan 9, just that the
> I/O system for pipes, network devices, etc. was descended from streams.
> That was the case at least as far back as 1990.
>
> Look at the early Plan 9 code for the pipe¹ and ethernet² devices, the
> code for Streams, Queues, and Blocks in port/stream.c³ and power/dat.h⁴,
> and tell me that doesn't descend from v8 streams. :)
>
> Also, thanks for Plan 9. It's lovely.
>
> Anthony
>
> 1. https://github.com/0intro/9hist/blob/13601b6f49db83aa369e382f5242927a46d2a433/port/devpipe.c
> 2. https://github.com/0intro/9hist/blob/13601b6f49db83aa369e382f5242927a46d2a433/port/devlance.c#L256
> 3. https://github.com/0intro/9hist/blob/13601b6f49db83aa369e382f5242927a46d2a433/port/stream.c
> 4. https://github.com/0intro/9hist/blob/13601b6f49db83aa369e382f5242927a46d2a433/power/dat.h#L338
prev parent reply other threads:[~2020-04-13 3:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-12 10:03 Paul Ruizendaal
2020-04-12 22:55 ` joe mcguckin
2020-04-14 14:54 ` Tony Finch
2020-04-12 23:15 ` Anthony Martin
2020-04-13 1:43 ` Rob Pike
2020-04-13 3:00 ` Anthony Martin
2020-04-13 3:14 ` Rob Pike [this message]
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='CAKzdPgzXtrbLD_te9GNRxOs82rZNh68dG0d_u=w=X9rmWgKmXw@mail.gmail.com' \
--to=robpike@gmail.com \
--cc=ality@pbrane.org \
--cc=pnr@planet.nl \
--cc=tuhs@minnie.tuhs.org \
/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).