From: forsyth@caldo.demon.co.uk
To: 9fans@cse.psu.edu
Subject: Re: [9fans] vfork and paging
Date: Tue, 2 Oct 2001 22:05:05 +0100 [thread overview]
Message-ID: <20011002211104.BDC9E199F3@mail.cse.psu.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 79 bytes --]
that restriction should go from Limbo fairly soon as well.
it's unmodular.
[-- Attachment #2: Type: message/rfc822, Size: 1616 bytes --]
From: "rob pike" <rob@plan9.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] vfork and paging
Date: Tue, 2 Oct 2001 15:25:07 -0400
Message-ID: <20011002192514.A243119A5F@mail.cse.psu.edu>
> the difficult part is flushing, of course.
Not any more. Alef had a restriction that a channel couldn't
be involved in two alts at once. The thread library has no
such restriction and flushing is now easy.
-rob
next reply other threads:[~2001-10-02 21:05 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-02 21:05 forsyth [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-10-19 21:03 David Gordon Hogan
2001-10-04 16:29 forsyth
2001-10-04 14:09 rog
2001-10-04 10:17 Richard Miller
2001-10-03 10:16 rog
2001-10-03 10:31 ` Boyd Roberts
2001-10-03 9:49 forsyth
2001-10-03 10:52 ` Boyd Roberts
2001-10-03 13:55 ` Borja Marcos
2001-10-03 14:23 ` Ronald G Minnich
2001-10-02 19:25 rob pike
2001-10-02 18:51 rog
2001-10-02 18:05 Russ Cox
2001-10-02 15:56 rob pike
2001-10-02 15:39 rog
2001-10-03 7:38 ` Boyd Roberts
2001-10-02 15:27 Fco.J.Ballesteros
2001-10-02 14:37 Sape Mullender
2001-10-02 14:31 rog
2001-10-02 14:29 presotto
2001-10-02 14:12 rog
2001-10-02 13:48 Sape Mullender
2001-10-02 13:47 rob pike
2001-10-02 13:42 Sape Mullender
2001-10-01 14:06 rob pike
2001-10-01 15:42 ` Douglas A. Gwyn
2001-10-01 14:01 forsyth
2001-10-01 12:21 rob pike
2001-10-02 8:27 ` Boyd Roberts
2001-10-02 13:34 ` Ronald G Minnich
2001-10-01 10:45 forsyth
2001-10-01 10:59 ` Boyd Roberts
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=20011002211104.BDC9E199F3@mail.cse.psu.edu \
--to=forsyth@caldo.demon.co.uk \
--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).