From: "Jörn Engel" <joern@wohnheim.fh-wedel.de>
To: Matthew Wilcox <matthew@wil.cx>
Cc: Jeff Layton <jlayton@redhat.com>, linux-fsdevel@vger.kernel.org
Subject: Re: [RFC][PATCH] ensure i_ino uniqueness in filesystems without permanent inode numbers (via idr)
Date: Wed, 15 Nov 2006 18:56:25 +0100 [thread overview]
Message-ID: <20061115175624.GE3399@wohnheim.fh-wedel.de> (raw)
In-Reply-To: <20061115172719.GK19143@parisc-linux.org>
On Wed, 15 November 2006 10:27:20 -0700, Matthew Wilcox wrote:
>
> I agree with these problems, but I liked your earlier approach to fixing
> them. I don't particularly like the idr approach because, as you say,
> it will reuse numbers rapidly.
Is that a problem for nfs only? Or are there others. For nfs, Jeff
already increments i_generation, so the (i_ino|i_generation) tupel is
not rapidly reused.
> Why is it these filesystems don't add their inodes to the hashtable?
> Might that not be a more profitable approach to fixing this problem?
To keep the hashtable small, as per hch's request.
Jörn
--
/* Keep these two variables together */
int bar;
-
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2006-11-15 17:57 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-14 20:22 [RFC][PATCH] ensure i_ino uniqueness in filesystems without permanent inode numbers (via idr) Jeff Layton
2006-11-14 20:26 ` Al Viro
2006-11-15 16:42 ` Jeff Layton
2006-11-15 16:44 ` Jeff Layton
2006-11-16 14:06 ` Al Viro
2006-11-16 14:34 ` Jeff Layton
2006-11-15 17:27 ` Matthew Wilcox
2006-11-15 17:56 ` Jörn Engel [this message]
2006-11-15 20:36 ` Jeff Layton
-- strict thread matches above, loose matches on Subject: below --
2006-12-01 14:48 Jeff Layton
2006-12-01 16:52 ` Randy Dunlap
2006-12-01 17:21 ` Jeff Layton
2006-12-01 17:42 ` Randy Dunlap
2006-12-02 5:30 ` Brad Boyer
2006-12-03 2:56 ` Jeff Layton
2006-12-02 12:58 ` Brad Boyer
2006-12-03 11:52 ` Al Boldi
2006-12-03 12:49 ` Jeff Layton
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=20061115175624.GE3399@wohnheim.fh-wedel.de \
--to=joern@wohnheim.fh-wedel.de \
--cc=jlayton@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=matthew@wil.cx \
/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).