From mboxrd@z Thu Jan 1 00:00:00 1970 From: Christoph Hellwig Subject: Re: [PATCH 15/18] fs: introduce a per-cpu last_ino allocator Date: Fri, 8 Oct 2010 06:03:46 -0400 Message-ID: <20101008100346.GA27737@infradead.org> References: <1286515292-15882-1-git-send-email-david@fromorbit.com> <1286515292-15882-16-git-send-email-david@fromorbit.com> <20101008095658.GA19804@ZenIV.linux.org.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Dave Chinner , linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org To: Al Viro Return-path: Received: from canuck.infradead.org ([134.117.69.58]:54455 "EHLO canuck.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753378Ab0JHKDu (ORCPT ); Fri, 8 Oct 2010 06:03:50 -0400 Content-Disposition: inline In-Reply-To: <20101008095658.GA19804@ZenIV.linux.org.uk> Sender: linux-fsdevel-owner@vger.kernel.org List-ID: On Fri, Oct 08, 2010 at 10:56:58AM +0100, Al Viro wrote: > FWIW, that one is begging to be split; what I mean is that there are > two classes of callers; ones that will set i_ino themselves anyway > and ones that really want i_ino invented. Two functions? There's no reason to add i_ino before adding it to the per-sb list, we don't do so either for inodes acquired via iget. The fix is simply to stop assigning i_ino in new_inode and call the helper to get it in the place that need it after the call to new_inode. Later we can even move to a lazy assignment scheme where needed. I'd also really like to get a grip on why the simple counters if fine for some filesystems while we need iunique() for others.