From: erik quanstrom <quanstro@coraid.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] 9P2000 and p9p
Date: Tue, 10 Apr 2007 22:55:10 -0400 [thread overview]
Message-ID: <cb68db4f0df442e9775bcaaa1c8fe598@coraid.com> (raw)
In-Reply-To: <461C45A4.3060909@tecmav.com>
> This is a different situation. In the example above read an write are
> done by one program and are from/to the same file server.
> The kernel knows where/when/what it reads/writes.
> A task "exec in kernel" (EMT also in Plan9 ? I don't know)
> one syscall at a time. To avoid the problem, the read after
> a write must be performed ignoring the EOD. The second read in
> a read-read seq must be short-circuited when the EOD is active.
> Each read sets the EOD (or time window) to guide the kernel for the next
> read.
>
i don't understand the problem you're trying to solve. this seems like
a special case. maybe as such, you want a protocol other than 9p.
the great thing about plan 9 is it's a way of working. it's not a protocol
or implementation.
- erik
next prev parent reply other threads:[~2007-04-11 2:55 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-10 17:12 Adriano Verardo
2007-04-10 17:39 ` Charles Forsyth
2007-04-10 18:14 ` Adriano Verardo
2007-04-10 19:33 ` C H Forsyth
2007-04-10 21:28 ` Adriano Verardo
2007-04-10 18:29 ` Russ Cox
2007-04-10 22:14 ` Adriano Verardo
2007-04-10 22:38 ` Charles Forsyth
2007-04-10 22:50 ` Russ Cox
2007-04-11 2:19 ` Adriano Verardo
2007-04-11 2:55 ` erik quanstrom [this message]
2007-04-11 3:10 ` Russ Cox
2007-04-11 6:58 ` Bruce Ellis
2007-04-11 8:20 ` Charles Forsyth
2007-04-11 15:38 ` ron minnich
2007-04-11 2:50 ` Kris Maglione
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=cb68db4f0df442e9775bcaaa1c8fe598@coraid.com \
--to=quanstro@coraid.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).