From: erik quanstrom <quanstro@quanstro.net>
To: sqweek@gmail.com, 9fans@9fans.net
Subject: Re: [9fans] 9p over high-latency
Date: Thu, 18 Sep 2008 07:51:44 -0400 [thread overview]
Message-ID: <0876d6a11c3a4fdd9b26e45e8e56abb2@quanstro.net> (raw)
> On Fri, Sep 12, 2008 at 7:47 PM, erik quanstrom <quanstro@quanstro.net> wrote:
> > as an aside: i don't think 9p itself limits plan 9 performance
> > over high-latency links. the limitations have more to do with
> > the number of outstanding messages, which is 1 in the mnt
> > driver.
>
> Hm, but what's the alternative here? Readahead seems somewhat
> attractive, if difficult (I worry about blocking reads and timing
> sensitive file systems). But there's one problem I can't resolve - how
> do you know what offset to Tread without consulting the previous
> Rread's count?
> Actually, I understand there has been discussion about grouping tags
> to allow for things like Twalk/Topen batching without waiting for
> Rwalk (which sounds like a great idea), maybe that would work here
> also...
the fundamental problem is that it becomes very difficult to
implement fileservers which don't serve up regular files.
you might make perminant changes to something stored on
a disk with readahead.
since one of the main points of plan 9 is to get rid of special
files, ioctl's and whatnot, read ahead seems unattactive.
i'll admit that i don't understand the point of batching walks.
i'm not sure why one would set up a case where you know you'll
have a long network and where you know you'll need to execute
a lot of walks. most applications that do most i/o in a particular
directory set . to that directory to avoid the walks.
i'm not sure that octopus wouldn't be better off optimizing
latency by running many more threads. but that's just an ignorant
opinion.
- erik
next reply other threads:[~2008-09-18 11:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-18 11:51 erik quanstrom [this message]
2008-09-18 13:34 ` Eric Van Hensbergen
[not found] <0a44b94d5b9fa0b13dc1d9ae11472e5e@quanstro.net>
2008-09-18 13:34 ` sqweek
2008-09-18 13:49 ` Eric Van Hensbergen
2008-09-18 17:26 ` Francisco J Ballesteros
2008-09-18 20:05 ` Steve Simon
2008-09-18 20:38 ` Francisco J Ballesteros
-- strict thread matches above, loose matches on Subject: below --
2008-09-18 9:57 sqweek
2008-09-18 10:36 ` Christian Kellermann
2008-09-18 10:48 ` Uriel
2008-09-27 1:17 ` Nathaniel W Filardo
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=0876d6a11c3a4fdd9b26e45e8e56abb2@quanstro.net \
--to=quanstro@quanstro.net \
--cc=9fans@9fans.net \
--cc=sqweek@gmail.com \
/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).