linux-kernel - Re: [PATCH 0/3] ensure unique i_ino in filesystems without permanent inode numbers (introduction)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <459174FB.3050107@redhat.com>
Date:	Tue, 26 Dec 2006 14:16:11 -0500
From:	Jeff Layton <jlayton@...hat.com>
To:	Jörn Engel <joern@...ybastard.org>,
	Christoph Hellwig <hch@...radead.org>
CC:	linux-kernel@...r.kernel.org, linux-fsdevel@...r.kernel.org
Subject: Re: [PATCH 0/3] ensure unique i_ino in filesystems without permanent
 inode numbers (introduction)

Jeff Layton wrote:
 >  >
 >  > 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
 >  >
 >
 >
 > A very good question. Certainly, just hashing them would be a heck of a
 > lot simpler. That was my first inclination when I looked at this, but as
 > you said, HCH NAK'ed that idea stating that it would bloat out the
 > hashtable. I tend to think that it's probably not that significant, but
 > that might very much depend on workload.
 >
 > I'm OK with either approach, though I'd like to have some sort of buyin
 > from Christoph on hashing the inodes before I start working on patches to
 > do that.
 >
 > Christoph, care to comment?
 >
 > -- Jeff
 >
 >

I'm still in limbo on this patchset and could use some guidance. It's not
clear to me that IDR is really a big enough win over just hashing the inodes.
It seems like the inode hash is pretty well optimized for fast lookups such
that even if we get some extra hash collisions it shouldn't be too awful.

Perhaps the best thing to do is to start with a patch that just hashes the
inodes and then fall back to using IDR (or some other scheme) if it turns out
that it impacts performance too much?

Anyone have an opinion on what approach they think would be best here?

-- Jeff

-
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/