From mboxrd@z Thu Jan 1 00:00:00 1970 From: Christoph Hellwig Subject: Re: [RFC 2/3] vfs: get_next_ino(), support for the uniqueness Date: Thu, 22 May 2014 17:14:31 +0200 Message-ID: <20140522151431.GA25517@lst.de> References: <1400698140-25853-1-git-send-email-hooanon05g@gmail.com> <1400698140-25853-3-git-send-email-hooanon05g@gmail.com> <20140522115657.GD7999@quack.suse.cz> <7078.1400771001@jrobl> <20140522151253.GH7999@quack.suse.cz> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: "J. R. Okajima" , linux-fsdevel@vger.kernel.org, adilger@dilger.ca, hch@lst.de, dchinner@redhat.com, viro@zeniv.linux.org.uk, jlbec@evilplan.org, gregkh@linuxfoundation.org, hughd@google.com To: Jan Kara Return-path: Received: from verein.lst.de ([213.95.11.211]:49491 "EHLO newverein.lst.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751088AbaEVPOf (ORCPT ); Thu, 22 May 2014 11:14:35 -0400 Content-Disposition: inline In-Reply-To: <20140522151253.GH7999@quack.suse.cz> Sender: linux-fsdevel-owner@vger.kernel.org List-ID: On Thu, May 22, 2014 at 05:12:53PM +0200, Jan Kara wrote: > Yes, that's why I wrote that if we find that uniqueness of inode numbers > in tmpfs is needed, then we should probably just make tmpfs add inodes to > hash list and use iunique(). That would seem like a better solution to me. Any reason not to just use the ida allocator for inode numbers in tmpfs?