From mboxrd@z Thu Jan 1 00:00:00 1970 From: Christoph Hellwig Subject: Re: [PATCH 13/18] fs: split locking of inode writeback and LRU lists Date: Sat, 16 Oct 2010 12:20:21 -0400 Message-ID: <20101016162021.GE16861@infradead.org> References: <1286515292-15882-1-git-send-email-david@fromorbit.com> <1286515292-15882-14-git-send-email-david@fromorbit.com> <20101008074243.GB24089@infradead.org> <20101008080018.GV4681@dastard> <20101008081816.GA17577@infradead.org> <20101016075713.GQ19147@amd> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Christoph Hellwig , Dave Chinner , linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org To: Nick Piggin Return-path: Content-Disposition: inline In-Reply-To: <20101016075713.GQ19147@amd> Sender: linux-kernel-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org On Sat, Oct 16, 2010 at 06:57:13PM +1100, Nick Piggin wrote: > > That needs some documentation both in the changelog and in the code > > I think. > > This is another instance where the irregular i_lock locking is making > these little subtleties to the locking. I think that is actually much > worse for maintainence/complexity than a few trylocks which can be > mostly removed with rcu anyway (which are obvious because of the well > documented lock order). Care to explain why? The I_FREEING and co checks are how we do things all over the icache for a long time. They are perfectly easy to understand concept. What I asked Dave about is documenting why he changed things here.