From: Eric Van Hensbergen <ericvh@gmail.com>
To: Al Viro <viro@parcelfarce.linux.theplanet.co.uk>
Cc: Miklos Szeredi <miklos@szeredi.hu>,
v9fs-developer@lists.sourceforge.net, kernel-mentors@selenic.com,
linux-fsdevel@vger.kernel.org, hch@infradead.org
Subject: Re: v9fs writepage
Date: Sat, 30 Apr 2005 13:47:35 -0500 [thread overview]
Message-ID: <a4e6962a050430114779b49d3d@mail.gmail.com> (raw)
In-Reply-To: <20050430183653.GE13052@parcelfarce.linux.theplanet.co.uk>
On 4/30/05, Al Viro <viro@parcelfarce.linux.theplanet.co.uk> wrote:
> On Sat, Apr 30, 2005 at 01:10:39PM -0500, Eric Van Hensbergen wrote:
>
> > It would seem a relaxed check in my v9fs_fid_locate would provide the
> > same service as keeping open files in the inode. We had looked at
> > doing something similar, but I hated the idea of having to keep the
> > extra book-keeping if there was another path (particularly since we
> > are already cacheing fids in dentries).
>
> a) 9P server is entirely within its rights to serve different contents
> depending on the implied uid and even on phase of moon during the processing
> of auth. So client-side file contents cache is not kosher.
>
Yes. I agree. I actually explicitly took all the cacheing behavior
out of v9fs when I started getting involved a year ago. I only put
the address_space operations back in recently in order to support mmap
(which isn't supported at all under Plan 9). Would you rather I
remove the vfs_addr.c support in order to stay more Plan 9 consistent?
I figured I'd have a better chance of getting LKML acceptance by
providing as many "linux semantics" as I could -- specifically we
really wanted to pass fsx.
>
> Putting the information about caching into 9P would be interesting, but
> that doesn't belong here - such stuff should be taken to Plan 9 maillist.
>
There is some precident for this in the cfs(4) file system under Plan
9 which providing something similar to the new Linux CacheFS for
non-synthetic file systems (a unofficial rule of thumb was that
anything that had a zero modification time was most likely synthetic
and therefore unsuitable to cache). My plan has been to start by
integrating this sort of layer on-top of the existing v9fs base and
then do what I can to remove any performance penalty from implementing
it as a stackable layer. I was also planning on talking to the linux
CacheFS guys to see if their stuff would be suitable for this
application. It's on the roadmap, but was planning to start after we
get the inital core accepted to the kernel (trying to keep things as
simple as possible). Its very likely we could just provide all mmap
support within the cache layer.
-eric
next prev parent reply other threads:[~2005-04-30 18:47 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-30 17:17 v9fs writepage Eric Van Hensbergen
2005-04-30 17:58 ` Miklos Szeredi
2005-04-30 18:10 ` Eric Van Hensbergen
2005-04-30 18:36 ` Al Viro
2005-04-30 18:47 ` Eric Van Hensbergen [this message]
2005-04-30 19:01 ` Al Viro
2005-04-30 20:03 ` Miklos Szeredi
2005-04-30 20:09 ` Al Viro
2005-04-30 21:44 ` Miklos Szeredi
2005-05-01 1:10 ` Eric Van Hensbergen
2005-05-01 15:36 ` [V9fs-developer] " Ronald G. Minnich
2005-05-01 15:29 ` Ronald G. Minnich
2005-04-30 19:53 ` Miklos Szeredi
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=a4e6962a050430114779b49d3d@mail.gmail.com \
--to=ericvh@gmail.com \
--cc=hch@infradead.org \
--cc=kernel-mentors@selenic.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=miklos@szeredi.hu \
--cc=v9fs-developer@lists.sourceforge.net \
--cc=viro@parcelfarce.linux.theplanet.co.uk \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.