9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@cse.psu.edu, Ronald G Minnich <rminnich@lanl.gov>
Subject: Re: [9fans] fuse bashing
Date: Wed, 25 Jan 2006 19:16:47 -0600	[thread overview]
Message-ID: <20060126011647.755F078FBD@dexter-peak.quanstro.net> (raw)
In-Reply-To: <43D79B60.5010006@lanl.gov>

one could write a fileserver that allows you to give it a file
to watch and either send a plumbmsg back or write a Dir
structure back on the original fd when it changes.

i'm not sure one needs to modify the underlying filesystem.

actually making the notifier live outside the filesystem would
allow many "notifiers" running against the same fs. say 1 fs
10 notifiers and 100 clients per notifier. 

- erik

Ronald G Minnich <rminnich@lanl.gov> writes

| 
| Dave Eckhardt wrote:
| >>The big complaints I know of so far on 9P are [...]
| > 
| > 
| > If servers routinely dealt with thousands of clients and/or
| > clients with large persistent caches then some sort of
| > acceleration for cache validation might be nice--callbacks
| > (aka leases) or maybe something based on a log of
| > invalidations.
| > 
| > But given current usage patterns it's not clear there's
| > a need.
| 
| 
| except here and some other sites, where there is a burning need, and 
| current parallel file systems are not quite working (yet)
| 
| having enough thousand nodes all try to stat the same file, at the same 
| time, in a callback-based file system, can be trouble.
| 
| 
| ron


  parent reply	other threads:[~2006-01-26  1:16 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-23 17:06 Russ Cox
2006-01-23 17:28 ` Ronald G Minnich
2006-01-23 17:44   ` David Leimbach
2006-01-23 18:07   ` Eric Van Hensbergen
2006-01-23 18:13     ` Bruce Ellis
2006-01-23 20:31   ` David Leimbach
2006-01-23 20:33     ` Ronald G Minnich
2006-01-23 23:28       ` Dan Cross
2006-01-23 23:53         ` David Leimbach
2006-01-24  0:07         ` Ronald G Minnich
2006-01-25 19:58         ` Enache Adrian
2006-01-25 20:30           ` Christoph Lohmann
2006-01-25 20:51             ` Ronald G Minnich
2006-01-25 21:09               ` Bruce Ellis
2006-01-25 20:50           ` Ronald G Minnich
2006-01-25 21:09             ` Enache Adrian
2006-01-24  0:12       ` John Barham
2006-01-25  5:29       ` Dave Eckhardt
2006-01-25 15:38         ` Ronald G Minnich
2006-01-25 21:31           ` Dave Eckhardt
2006-01-26  1:16           ` erik quanstrom [this message]
2006-01-25  5:30       ` Dave Eckhardt
2006-01-25  7:46         ` Jack Johnson
2006-01-25  8:11           ` Lyndon Nerenberg
2006-01-25  8:18             ` Lyndon Nerenberg
2006-01-25  9:46             ` Andriy G. Tereshchenko
2006-01-25 15:45         ` Ronald G Minnich
2006-01-23 17:51 ` C H Forsyth
2006-01-23 17:46   ` David Leimbach
2006-01-23 20:08     ` Ronald G Minnich
2006-01-23 18:46   ` Skip Tavakkolian
2006-01-24  2:22 ` Latchesar Ionkov
2006-01-24  8:37   ` Charles Forsyth
2006-01-24  9:41     ` Charles Forsyth
2006-01-24 10:04       ` Charles Forsyth
     [not found] <000001c620ca$f86f1570$14aaa8c0@utelsystems.local>
2006-01-24  9:46 ` "Nils O. Selåsdal"
2006-01-24 20:10 quanstro
2006-01-24 21:37 ` Eric Van Hensbergen
2006-01-24 23:14   ` Charles Forsyth
2006-01-25  0:26   ` Latchesar Ionkov
2006-01-25  0:25 ` Latchesar Ionkov
2006-01-25  1:31   ` erik quanstrom
2006-01-25  1:40     ` Latchesar Ionkov
2006-01-25  1:42       ` Eric Van Hensbergen

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=20060126011647.755F078FBD@dexter-peak.quanstro.net \
    --to=quanstro@quanstro.net \
    --cc=9fans@cse.psu.edu \
    --cc=rminnich@lanl.gov \
    /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).