linux-kernel - Re: [PATCH] fs: inode per-cpu last

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <20101001061215.GJ32349@infradead.org>
Date:	Fri, 1 Oct 2010 02:12:15 -0400
From:	Christoph Hellwig <hch@...radead.org>
To:	Eric Dumazet <eric.dumazet@...il.com>
Cc:	Andrew Morton <akpm@...ux-foundation.org>,
	Dave Chinner <david@...morbit.com>,
	linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] fs: inode per-cpu last_ino allocator

Eric,

what workload did this matter for?  As mentioned elsewhere we don't
actually need to set i_ino in new_inode in many cases.  Normal
disk/network filesystem already set their own i_ino anyway and don't
need it at all.  Various in-kernel filesystems don't need any valid
i_ino and Nick's full series actually has a patch dealing with it,
which only leaves various user-mountable syntetic filesystems that
want to generate an inode number, and IMHO they're better off using
iunique.

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