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 11:43:03 +1000 [thread overview]
Message-ID: <CAKzdPgyGk3jYyVjs3hkdqQWhKyPyhGGCCGG8kq2G9BAJYtUH+g@mail.gmail.com> (raw)
In-Reply-To: <20200412231503.GA48389@alice>
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.
-rob
On Mon, Apr 13, 2020 at 9:16 AM Anthony Martin <ality@pbrane.org> wrote:
>
> As an aside, Plan 9 began with a descendant of dmr's streams
> but replaced it in mid-1993 with a simple queued i/o scheme.
> This was done for performance and to simplify the code since
> they didn't end up using much of the streams functionality.
>
> Anthony
next prev parent reply other threads:[~2020-04-13 1:43 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 [this message]
2020-04-13 3:00 ` Anthony Martin
2020-04-13 3:14 ` Rob Pike
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=CAKzdPgyGk3jYyVjs3hkdqQWhKyPyhGGCCGG8kq2G9BAJYtUH+g@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).