[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20090618125002.GA50695@dspnet.fr.eu.org>
Date: Thu, 18 Jun 2009 14:50:02 +0200
From: Olivier Galibert <galibert@...ox.com>
To: David Howells <dhowells@...hat.com>
Cc: Al Viro <viro@...IV.linux.org.uk>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Andreas Dilger <adilger@....com>,
Alan Cox <alan@...rguk.ukuu.org.uk>, akpm@...ux-foundation.org,
linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-afs@...ts.infradead.org
Subject: Re: [PATCH 00/17] [RFC] AFS: Implement OpenAFS pioctls(version)s
On Wed, Jun 17, 2009 at 08:28:29PM +0100, David Howells wrote:
> Al Viro <viro@...IV.linux.org.uk> wrote:
>
> > ... so we need a syscall that would do that "drop the caches" operation.
> > _After_ having decided that it's really needed for symlinks.
>
> If you want to support disconnected operation, then you need a way to (a) lock
> an object in the cache, (b) unlock an object in the cache, (c) pull an object
> into the cache, (d) kick an object out of the cache, (e) ban an object from the
> cache, (f) reserve space in the cache for an object, (g) release the
> reservation on an object and (h) find out the lock/ban/reservation status of an
> object in the cache, and you'd need to support them for _all_ file types,
> including dirs, symlinks, dev files and fifos. Probably not UNIX sockets,
> though.
If I follow correctly, what you call "object" is "anything a name can
point to in a filesystem", and you need to be able to refer to any of
them without side effects. So, Al, whay should be used to refer to
them?
OG.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists