public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andreas Dilger <adilger@clusterfs.com>
To: Ion Badulescu <ionut@cs.columbia.edu>,
	"Peter J. Braam" <braam@clusterfs.com>
Cc: Urban Widmark <urban@teststation.com>,
	linux-kernel@vger.kernel.org,
	Jean-Eric Cuendet <jean-eric.cuendet@linkvest.com>
Subject: Re: intent-based lookups (was Re: SMB filesystem)
Date: Mon, 3 Jun 2002 17:03:56 -0600	[thread overview]
Message-ID: <20020603230356.GG18668@turbolinux.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0206022319290.27283-100000@cola.enlightnet.local> <200206032245.g53Mji123739@buggy.badula.org>

On Jun 03, 2002  18:45 -0400, Ion Badulescu wrote:
> On Sun, 2 Jun 2002 23:34:59 +0200 (CEST), Urban Widmark <urban@teststation.com> wrote:
> 
> > Currently autofs has a problem where it won't show the mountpoints of
> > non-mounted directories, but I think you would run into that problem too.
> > (short version of the problem: how do you prevent 'ls -l' from mounting
> > all filesystems in a directory?)
> 
> You add the concept of a "light" lookup, and you make path_walk() call this
> "light" lookup (be that a separate fs method, or a flag passed down to real
> lookup()) iff the path component being looked up is the last component in 
> the path. A "light" lookup sets a flag in the inode signalling that the inode
> is incomplete, so cached_lookup() can check this flag and call a "full"
> lookup() (or perhaps a "full" revalidate()) if necessary.
> 
> The actual details need to be thought out a bit more, this is only a general
> outline. In particular, we need a bullet-proof way to determine when to
> "upgrade" the inode from "light" to "full".

This may fit nicely with some work we are doing for Lustre (a scalable
distributed filesystem for Linux) which needs to do "intent-based
lookups".  It has a similar desire to separate the lookups of the start
of the path from the lookup of the last component of the path.  Peter
Braam (CC'd) has a patch for 2.4.18 which implements this.  I pass the
discussion over to him...

Cheers, Andreas
--
Andreas Dilger
http://www-mddsp.enel.ucalgary.ca/People/adilger/
http://sourceforge.net/projects/ext2resize/


      reply	other threads:[~2002-06-03 23:06 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-02 21:00 SMB filesystem Jean-Eric Cuendet
2002-06-02 21:16 ` Thunder from the hill
2002-06-02 21:21 ` Matti Aarnio
2002-06-02 21:31 ` Marius Gedminas
2002-06-02 21:34 ` Urban Widmark
2002-06-02 22:16   ` Marius Gedminas
2002-06-03 22:45   ` Ion Badulescu
2002-06-03 23:03     ` Andreas Dilger [this message]

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=20020603230356.GG18668@turbolinux.com \
    --to=adilger@clusterfs.com \
    --cc=braam@clusterfs.com \
    --cc=ionut@cs.columbia.edu \
    --cc=jean-eric.cuendet@linkvest.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=urban@teststation.com \
    /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