From: "Steve Simon" <steve@quintile.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] 9P optimization
Date: Sun, 24 Jun 2007 12:38:25 +0100 [thread overview]
Message-ID: <c9581c30b17957fb7a0e819d5343af96@quintile.net> (raw)
In-Reply-To: <20070624030145.P1471@orthanc.ca>
> I loath the idea of pushing state into 9P, but I wonder if a combination
> of client side cfs with a kqueue-like 'file is modified' server event
> might not solve most of the problem. Layered into aan perhaps?
Not sure if I missunderstand you but I am _not_ suggesting pushing any
state into p9.
My thoughts where modifying cfs heuristics to reduce the probability of
waiting for a coherence check (which could be quite a few RTTs).
In the limit I also suggested providing a synthetic file which contains
dirstat(1) info on modified files as they change - which I think is what
you mean by a "kqueue-like 'file is modified' server".
The problem with implementing this as a server program on the fileserver machine
is that _all_ fossil/kfs/kenfs file accesses would have to pass through this server
to be sure that a when a file is changed by somone else you are informed.
As fossil (what I use) already knows this info I thougt it would be as well for it
to provide this file itself.
hope this clarifies.
-Steve
next prev parent reply other threads:[~2007-06-24 11:38 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-19 20:11 [9fans] About 9P Philippe Anel
2007-06-20 0:37 ` Russ Cox
2007-06-20 2:06 ` Roman Shaposhnick
2007-06-20 11:29 ` Anthony Sorace
2007-06-22 0:32 ` Derek Fawcus
2007-06-22 6:58 ` Philippe Anel
2007-06-22 15:57 ` Derek Fawcus
2007-06-22 20:32 ` Philippe Anel
2007-06-22 21:10 ` David Leimbach
2007-06-22 21:35 ` Philippe Anel
2007-06-22 21:46 ` David Leimbach
2007-06-22 21:55 ` Philippe Anel
2007-06-22 22:25 ` Philippe Anel
2007-06-22 22:57 ` David Leimbach
2007-06-22 23:01 ` Anant Narayanan
2007-06-23 4:30 ` Russ Cox
2007-06-23 5:10 ` Skip Tavakkolian
2007-06-23 9:25 ` Francisco J Ballesteros
2007-06-23 15:50 ` Martin Atkins
2007-06-23 6:24 ` Philippe Anel
2007-06-23 15:00 ` Rob Pike
2007-06-24 0:52 ` [9fans] 9P optimization Lyndon Nerenberg
2007-06-24 3:04 ` Francisco J Ballesteros
2007-06-24 3:15 ` Lyndon Nerenberg
2007-06-24 4:08 ` ron minnich
2007-06-24 9:34 ` Steve Simon
2007-06-24 10:06 ` Lyndon Nerenberg
2007-06-24 11:38 ` Steve Simon [this message]
2007-06-24 13:34 ` Lyndon Nerenberg
2007-06-25 0:34 ` ron minnich
2007-06-25 17:53 ` Lyndon Nerenberg
2007-06-25 1:02 ` Dave Eckhardt
2007-06-24 12:14 ` erik quanstrom
2007-06-24 13:36 ` Lyndon Nerenberg
2007-06-24 21:47 ` erik quanstrom
2007-06-25 17:48 ` Lyndon Nerenberg
2007-06-25 18:46 ` erik quanstrom
2007-06-24 4:16 ` Bruce Ellis
2007-06-24 18:05 ` Skip Tavakkolian
2007-06-22 23:20 ` [9fans] About 9P Skip Tavakkolian
2007-06-22 23:48 ` Francisco J Ballesteros
2007-06-23 0:27 ` Roman Shaposhnick
2007-06-23 0:27 ` Francisco J Ballesteros
2007-06-23 12:08 ` erik quanstrom
2007-06-23 12:27 ` Francisco J Ballesteros
2007-06-23 12:57 ` Lucio De Re
2007-06-23 13:01 ` Uriel
2007-06-23 13:36 ` Francisco J Ballesteros
2007-06-23 14:27 ` Lucio De Re
2007-06-23 14:45 ` Francisco J Ballesteros
2007-06-22 21:16 ` Skip Tavakkolian
2007-06-22 21:37 ` Philippe Anel
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=c9581c30b17957fb7a0e819d5343af96@quintile.net \
--to=steve@quintile.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).