From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nick Piggin Subject: Re: [PATCH 18/18] fs: do not assign default i_ino in new_inode Date: Sat, 16 Oct 2010 18:57:28 +1100 Message-ID: <20101016075728.GT19147@amd> References: <1286928961-15157-1-git-send-email-david@fromorbit.com> <1286928961-15157-19-git-send-email-david@fromorbit.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org To: Dave Chinner Return-path: Content-Disposition: inline In-Reply-To: <1286928961-15157-19-git-send-email-david@fromorbit.com> Sender: linux-kernel-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org On Wed, Oct 13, 2010 at 11:16:01AM +1100, Dave Chinner wrote: > From: Christoph Hellwig > > Instead of always assigning an increasing inode number in new_inode > move the call to assign it into those callers that actually need it. > For now callers that need it is estimated conservatively, that is > the call is added to all filesystems that do not assign an i_ino > by themselves. For a few more filesystems we can avoid assigning > any inode number given that they aren't user visible, and for others > it could be done lazily when an inode number is actually needed, > but that's left for later patches. My patch for this reduces churn by just adding a new function instead. The last_ino allocator is really fast now, so IMO it was not worth the churn to go through filesystems; just let them do it.