From: David Howells <dhowells@redhat.com>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: David Howells <dhowells@redhat.com>,
torvalds@osdl.org, akpm@osdl.org, steved@redhat.com,
aviro@redhat.com, linux-fsdevel@vger.kernel.org,
linux-cachefs@redhat.com, nfsv4@linux-nfs.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 5/6] NFS: Unify NFS superblocks per-protocol per-server [try #7]
Date: Thu, 09 Mar 2006 11:27:40 +0000 [thread overview]
Message-ID: <23847.1141903660@warthog.cambridge.redhat.com> (raw)
In-Reply-To: <1141858122.11378.15.camel@lade.trondhjem.org>
Trond Myklebust <trond.myklebust@fys.uio.no> wrote:
> > The attached patch makes NFS share superblocks between mounts from the same
> > server over the same protocol.
>
> We want to make NFS share superblocks on a per-filesystem basis, rather
> than forcing it into a per-server basis.
By "per-filesystem", I presume you mean per-server-mounted-filesystem?
Something like what the kAFS client tries to do. As it happens the current NFS
code doesn't do this either, but it has occurred to me that this would be
useful, just not necessarily easy...
> Cachefs may like the latter, but POSIX does not like a filesystem where
> inode numbers are not guaranteed to be unique.
I don't like it either, but the situation is already present.
Note that CacheFS would be happy with the former too, just as long as the keys
it is given don't end up aliasing.
> A unique per-server superblock also makes it hard to support features
> like failover onto replicated filesystems and/or migration of individual
> filesystems onto another server.
So you want these patches dropping?
Note that you can't necessarily do what you want with the current code either.
David
next prev parent reply other threads:[~2006-03-09 11:27 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-08 20:30 [PATCH 1/6] NFS: Permit filesystem to override root dentry on mount [try #7] David Howells
2006-03-08 20:30 ` [PATCH 2/6] 9p: Fix error handling on superblock alloc failure " David Howells
2006-03-08 21:28 ` Christoph Hellwig
2006-03-08 20:30 ` [PATCH 3/6] NFS: Abstract out namespace initialisation " David Howells
2006-03-08 20:32 ` Christoph Hellwig
2006-03-08 20:30 ` [PATCH 4/6] NFS: Add dentry materialisation op " David Howells
2006-03-08 21:31 ` Christoph Hellwig
2006-03-08 20:30 ` [PATCH 5/6] NFS: Unify NFS superblocks per-protocol per-server " David Howells
2006-03-08 21:23 ` Christoph Hellwig
2006-03-08 22:48 ` Trond Myklebust
2006-03-09 11:27 ` David Howells [this message]
2006-03-08 20:30 ` [PATCH 6/6] Optimise d_find_alias() " David Howells
2006-03-08 21:14 ` [PATCH] NFS: Make namespace initialisation out of line David Howells
2006-03-08 21:25 ` [PATCH 1/6] NFS: Permit filesystem to override root dentry on mount [try #7] Christoph Hellwig
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=23847.1141903660@warthog.cambridge.redhat.com \
--to=dhowells@redhat.com \
--cc=akpm@osdl.org \
--cc=aviro@redhat.com \
--cc=linux-cachefs@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nfsv4@linux-nfs.org \
--cc=steved@redhat.com \
--cc=torvalds@osdl.org \
--cc=trond.myklebust@fys.uio.no \
/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).