From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] The Web9 Project
Date: Sun, 9 Sep 2007 08:18:49 -0400 [thread overview]
Message-ID: <fbc8e61f6c5d9bd4c6309bd7a88b41b6@quanstro.net> (raw)
In-Reply-To: <8ccc8ba40709090503q38577a98v351702557dce67e1@mail.gmail.com>
> The problem is that you need, in a way, to break 9p. You need readahead, you
> need to bundle requests, and you need to cache in a very careful way.
the way i read the protocol, 9p does support readahead. Tread
takes tag, fid, offset, count. i can have up to 64k tags, so i think
this means i can have up to 64k outstanding reads. what am i missing?
why do we need to bundle requests? that seems like the wrong level.
in effect, that is creating an execution environment on the fs.
if latency is that bad and readahead won't work because the files
are too small, why not treat the remote storage as a block device
and run the fs locally? the "fs" could be a simple flat file.
this seems much simplier for most applications. no fid cache mapping
problem. and it reuses
- erik
next prev parent reply other threads:[~2007-09-09 12:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <EE662DC3-5A6C-45BB-8623-A569338F4C46@kix.in>
2007-09-08 12:39 ` Enrico Weigelt
2007-09-08 19:38 ` Anant Narayanan
2007-09-08 15:45 ` Skip Tavakkolian
2007-09-08 19:46 ` Anant Narayanan
2007-09-08 20:15 ` Uriel
2007-09-09 3:46 ` Latchesar Ionkov
2007-09-09 9:44 ` Francisco J Ballesteros
2007-09-09 11:55 ` erik quanstrom
2007-09-09 12:03 ` Francisco J Ballesteros
2007-09-09 12:18 ` erik quanstrom [this message]
2007-09-09 12:52 ` Francisco J Ballesteros
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=fbc8e61f6c5d9bd4c6309bd7a88b41b6@quanstro.net \
--to=quanstro@quanstro.net \
--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).