linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Nikita Danilov <nikita@clusterfs.com>
To: Bryan Henderson <hbryan@us.ibm.com>
Cc: fsdevel <linux-fsdevel@vger.kernel.org>,
	Shaya Potter <spotter@cs.columbia.edu>,
	nfsv4 <nfsv4@linux-nfs.org>,
	Dave Kleikamp <shaggy@austin.ibm.com>
Subject: Re: [RFC] Support for stackable file systems on top of nfs
Date: Fri, 11 Nov 2005 19:40:56 +0300	[thread overview]
Message-ID: <17268.51608.767900.660180@gargle.gargle.HOWL> (raw)
In-Reply-To: <OF487069B4.4E117BBF-ON882570B5.0080FA0C-882570B6.0001232D@us.ibm.com>

Bryan Henderson writes:

[...]

 > 
 > I've always been irritated by the fact that filesystem drivers see struct 
 > file at all.  struct file ought to live in a higher 
 > filesystem-type-independent layer, with the filesystem driver seeing just 
 > inodes.  

This is how *BSD VFS works, and it is a pain in the neck. For example,
implementing file-system-type specific read-ahead algorithm requires
jumping through all kinds of loops, because such algorithm works with
data (read-ahead window parameters) that naturally tend to be stored in
the file descriptor, and the latter is invisible to the file-system
code.

 >          Why are credentials cached in the struct file?  Is that a natural 
 > place for it or just what's available?
 > 
 > --
 > Bryan Henderson                     IBM Almaden Research Center
 > San Jose CA                         Filesystems

Nikita.

  parent reply	other threads:[~2005-11-11 16:40 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-10 17:32 [RFC] Support for stackable file systems on top of nfs Dave Kleikamp
2005-11-10 20:07 ` Christoph Hellwig
2005-11-10 21:35   ` John T. Kohl
2005-11-10 21:40     ` Shaya Potter
2005-11-10 21:57       ` John T. Kohl
2005-11-10 21:50     ` Christoph Hellwig
2005-11-11  2:31     ` Trond Myklebust
2005-11-11  4:04       ` Trond Myklebust
2005-11-11 13:45         ` John T. Kohl
2005-11-11 15:27           ` Charles P. Wright
2005-11-11 17:38             ` John T. Kohl
2005-11-14 15:56     ` David Howells
2005-11-10 21:24 ` Trond Myklebust
2005-11-10 21:36   ` Shaya Potter
2005-11-10 22:18     ` Trond Myklebust
2005-11-10 22:27       ` Shaya Potter
2005-11-10 22:40         ` Trond Myklebust
2005-11-11  0:12           ` Bryan Henderson
2005-11-11  1:30             ` Brad Boyer
2005-11-11  2:06             ` Trond Myklebust
2005-11-11 18:18               ` Bryan Henderson
2005-11-11 19:22                 ` Trond Myklebust
2005-11-11 21:57                   ` Bryan Henderson
2005-11-11 22:41                     ` Trond Myklebust
2005-11-14 19:02                       ` Bryan Henderson
2005-11-11 16:40             ` Nikita Danilov [this message]
2005-11-11 18:45               ` Bryan Henderson
2005-11-11 19:31                 ` Nikita Danilov
2005-11-11 19:42                   ` Trond Myklebust
2005-11-11 23:13                   ` Bryan Henderson
  -- strict thread matches above, loose matches on Subject: below --
2005-11-14  0:44 Nikolai Joukov
2005-11-14 16:02 ` David Howells
2005-11-14 20:48   ` Erez Zadok
2005-11-14 21:13     ` John T. Kohl
2005-11-14 21:32       ` Jamie Lokier
2005-11-14 16:11 ` John T. Kohl

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=17268.51608.767900.660180@gargle.gargle.HOWL \
    --to=nikita@clusterfs.com \
    --cc=hbryan@us.ibm.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=nfsv4@linux-nfs.org \
    --cc=shaggy@austin.ibm.com \
    --cc=spotter@cs.columbia.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).