From: rog@vitanuova.com
To: 9fans@cse.psu.edu
Subject: Re: [9fans] design clairvoyance & the 9 way
Date: Thu, 8 May 2003 18:45:57 +0100 [thread overview]
Message-ID: <61a8da7f32d9ffc6121bba498dc612ba@vitanuova.com> (raw)
In-Reply-To: <7f7d37e3f08741687eaa3b7c910e3cf6@plan9.bell-labs.com>
> Processes that want to do a
> lot of overlapped I/O can exportfs("/") and then interact
> with their name space via 9P messages, avoiding the
> need for lots of slave procs to manage just to run I/O.
wouldn't you then need the slave procs on the server side, anyway? as
you'd need to avoid blocking a device because its client wasn't
reading the message... unless you added asynchronous writes, i
suppose.
> For example, the SCSI driver
> could easily look at the 9P queue and do disk scheduling or
> issue multiple SCSI requests at once.
surely it could anyway? just give it a proc to itself, and have the
various device entry points queue messages, which could then be
inspected in much the same way.
next prev parent reply other threads:[~2003-05-08 17:45 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-08 15:33 jmk
2003-05-08 15:41 ` David Presotto
2003-05-08 16:21 ` rog
2003-05-08 16:27 ` Russ Cox
2003-05-08 16:52 ` rog
2003-05-08 16:25 ` Russ Cox
2003-05-08 17:45 ` rog [this message]
2003-05-08 18:33 ` Russ Cox
-- strict thread matches above, loose matches on Subject: below --
2003-05-07 16:32 C (Was: [9fans] same functions everywhere) northern snowfall
2003-05-07 16:33 ` [9fans] design clairvoyance & the 9 way Sam
2003-05-07 17:34 ` Fco.J.Ballesteros
2003-05-07 20:01 ` David Presotto
2003-05-07 20:34 ` Stephen Wynne
2003-05-07 21:57 ` Steve Kotsopoulos
2003-05-08 4:14 ` A.S. Kukhar
2003-05-08 17:04 ` Dan Cross
2003-05-09 19:14 ` boyd, rounin
2003-05-07 22:33 ` Sam
2003-05-08 0:46 ` northern snowfall
2003-05-08 16:04 ` Sam
2003-05-08 17:08 ` Russ Cox
2003-05-09 1:12 ` Geoff Collyer
2003-05-08 17:26 ` Dan Cross
2003-05-09 1:12 ` northern snowfall
2003-05-09 0:49 ` Dan Cross
2003-05-09 1:07 ` Joel Salomon
2003-05-09 2:53 ` ron minnich
2003-05-09 8:36 ` Douglas A. Gwyn
2003-05-09 14:29 ` ron minnich
2003-05-09 15:41 ` northern snowfall
2003-05-09 2:18 ` northern snowfall
2003-05-09 7:55 ` Taj Khattra
2003-05-09 9:48 ` northern snowfall
2003-05-09 19:52 ` boyd, rounin
2003-05-09 20:47 ` David Presotto
2003-05-10 2:56 ` boyd, rounin
2003-05-14 18:55 ` boyd, rounin
2003-05-08 4:04 ` Russ Cox
2003-05-08 0:20 ` northern snowfall
2003-05-19 9:46 ` boyd, rounin
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=61a8da7f32d9ffc6121bba498dc612ba@vitanuova.com \
--to=rog@vitanuova.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).