From: Adriano Verardo <a.verardo@tecmav.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] 9P2000 and p9p
Date: Wed, 11 Apr 2007 00:14:09 +0200 [thread overview]
Message-ID: <461C0C31.80000@tecmav.com> (raw)
In-Reply-To: <20070410182940.6EC861E8C3B@holo.morphisms.net>
Russ Cox wrote:
> As Charles pointed out, what you describe is in fact
> the behavior of fread(3) (from stdio) but is not the
> behavior of the underlying read(2) system call,
> even on Unix. An EOD flag can't work without
> either (a) changing the system call interface or
> (b) having some kind of lease so that the EOD can
> be invalidated when more data comes in between
> the first read and the second read (which you
> propose the operating system should answer without
> reference to the 9P server).
It depends on the time between the two read.
If they were within a few time slices the second
one could return 0 without Tread to to the file server.
The data coming in between the first and second
read is (IMO) a false problem. All would go as the new data
were arrived just after the second (true) read to the file server.
> The extra fids you see when mounting under Linux
> don't grow without bound.
With an infinite loop of "lc /n/adri" the max is 8630 for
a FreeBSD p9p session. Ok (!?) for RTEMS|VxWorks|eCos|... on x86, not
for a mCtrl.
Clients under Plan9 would be "the" solution, but sometimes Lunix
is a must.
Adriano
next prev parent reply other threads:[~2007-04-10 22:14 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 [this message]
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
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=461C0C31.80000@tecmav.com \
--to=a.verardo@tecmav.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).