9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: C H Forsyth <forsyth@vitanuova.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] 9P2000 and p9p
Date: Tue, 10 Apr 2007 20:33:12 +0100	[thread overview]
Message-ID: <9f436e85a50e21861fc0871595bfb995@vitanuova.com> (raw)
In-Reply-To: <461BD411.9020107@tecmav.com>

>Could a EOD field in Rread be useful ? In some cases it would avoid
>a lot of messages. I think a very small servers (mController) and low
>channels.

yes, although we didn't find it a huge problem on the lego brick,
but then again the timing constraints were fairly lax, even for the lego clock.
we did run a zero-compressing run-length-encoding scheme to compress stat entries
(lots of 28 byte NAMELEN things) and thus directories, but that would have been
less necessary with the current 9p2000/styx encoding; if perhaps still useful.

perhaps more helpfully, note that when reading /dev/time, for instance or especially /dev/bintime,
the application (typically a library function, but not always),
only expects one record, and does just one read, causing just one Tread. cat still works though,
even though it does one extra read (that returns 0).  that's true for some other files too.


  reply	other threads:[~2007-04-10 19:33 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 [this message]
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
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=9f436e85a50e21861fc0871595bfb995@vitanuova.com \
    --to=forsyth@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).