From: Jeff Layton <jlayton@redhat.com>
To: "Jörn Engel" <joern@wohnheim.fh-wedel.de>
Cc: Matthew Wilcox <matthew@wil.cx>, 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 15:36:29 -0500 [thread overview]
Message-ID: <1163622989.3917.6.camel@tleilax.poochiereds.net> (raw)
In-Reply-To: <20061115175624.GE3399@wohnheim.fh-wedel.de>
On Wed, 2006-11-15 at 18:56 +0100, Jörn Engel wrote:
> To keep the hashtable small, as per hch's request.
Adding to the hashtable was my first suggestion (and actually it still
seems reasonable to me), but according to hch, the reason most of these
filesystems don't add their inodes to the hashtable is that they are
generally pinned in memory. Adding them might slow down inode lookups
for filesystems that don't pin their inodes.
Still, even though they're pinned, we need to keep track of them somehow
to know that i_ino is unique. idr is one way, but there are certainly
others. Another approach would be to add a entirely separate hashtable
for these inodes, but I figured I'd try this way first.
-- Jeff
-
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 20:36 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
2006-11-15 20:36 ` Jeff Layton [this message]
-- 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=1163622989.3917.6.camel@tleilax.poochiereds.net \
--to=jlayton@redhat.com \
--cc=joern@wohnheim.fh-wedel.de \
--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).