From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <61a8da7f32d9ffc6121bba498dc612ba@vitanuova.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] design clairvoyance & the 9 way
From: rog@vitanuova.com
In-Reply-To: <7f7d37e3f08741687eaa3b7c910e3cf6@plan9.bell-labs.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Date: Thu,  8 May 2003 18:45:57 +0100
Topicbox-Message-UUID: a4ed1278-eacb-11e9-9e20-41e7f4b1d025

> 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.