From: "Jörn Engel" <joern@lazybastard.org>
To: Jeff Layton <jlayton@redhat.com>
Cc: akpm@osdl.org, linux-kernel@vger.kernel.org,
linux-fsdevel@vger.kernel.org,
Christoph Hellwig <hch@infradead.org>
Subject: Re: [PATCH 0/3] ensure unique i_ino in filesystems without permanent inode numbers (introduction)
Date: Fri, 15 Dec 2006 14:00:57 +0000 [thread overview]
Message-ID: <20061215140057.GF30508@lazybastard.org> (raw)
In-Reply-To: <45829D94.1090304@redhat.com>
On Fri, 15 December 2006 08:05:24 -0500, Jeff Layton wrote:
> Jeff Layton wrote:
> > Apologies for the long email, but I couldn't come up with a way to explain
> > this in fewer words. Many filesystems that are part of the linux kernel
> > have problems with how they have assign out i_ino values:
> >
>
> If there are no further comments/suggestions on this patchset, I'd like to
> ask Andrew to add it to -mm soon and target getting it rolled into 2.6.21.
I'm still unsure whether idr has a sufficient advantage over simply
hashing the inodes. Hch has suggested that keeping the hashtable
smaller is good for performance. But idr adds new complexity, which
should be avoided on its own right. So is the performance benefit big
enough to add more complexity? Is it even measurable?
Jörn
--
Fancy algorithms are buggier than simple ones, and they're much harder
to implement. Use simple algorithms as well as simple data structures.
-- Rob Pike
-
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-12-15 14:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-07 22:12 [PATCH 0/3] ensure unique i_ino in filesystems without permanent inode numbers (introduction) Jeff Layton
2006-12-15 13:05 ` Jeff Layton
2006-12-15 14:00 ` Jörn Engel [this message]
2006-12-15 15:01 ` Jeff Layton
2006-12-26 19:16 ` 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=20061215140057.GF30508@lazybastard.org \
--to=joern@lazybastard.org \
--cc=akpm@osdl.org \
--cc=hch@infradead.org \
--cc=jlayton@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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).