From: Dan Clark dlc@ncube.com
Subject: [9fans] plan9 extensions
Date: Fri, 15 Aug 1997 10:48:44 -0700 [thread overview]
Message-ID: <19970815174844.7DhlsmAgGXNONurZDCmO6spUPm-80C1Yc4aeqRsb-JI@z> (raw)
The synchronous copy everything model in plan9 might be extended for
performance reasons to include such primitives as asynchronous i/o and
pre-formatted vector read/write operations. Has any thought been given
in the plan9 community as to a generic interface for asynchronous i/o?
Although it is trivial to implement efficient asynchronous i/o in a particular
driver perhaps it would be best to have a generic interface for all i/o,
including communications and scsi subsystems. Some measurements indicate
that utilizing light weight processes for achieving asynchronous behavior
may not have the desired performance characteristics.
Has Brazil (or any future development) at Lucent given any thought to this
matter? Your insights and suggestions are most welcome.
danc
Dan L. Clark dlc@ncube.com 503/531-6432
nCUBE, 1825 NW 167th Place, Beaverton, OR 97006
next reply other threads:[~1997-08-15 17:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-08-15 17:48 Dan [this message]
-- strict thread matches above, loose matches on Subject: below --
1997-08-15 18:39 forsyth
1997-08-15 16:22 forsyth
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=19970815174844.7DhlsmAgGXNONurZDCmO6spUPm-80C1Yc4aeqRsb-JI@z \
--to=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).