From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1761525AbZEANcy (ORCPT ); Fri, 1 May 2009 09:32:54 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1763339AbZEANbx (ORCPT ); Fri, 1 May 2009 09:31:53 -0400 Received: from mail-ew0-f176.google.com ([209.85.219.176]:32880 "EHLO mail-ew0-f176.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1763351AbZEANbv (ORCPT ); Fri, 1 May 2009 09:31:51 -0400 DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=date:from:to:cc:subject:message-id:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; b=r63Wa7BxzYJjd9x1vGPO85RvooKi12ZV2+DlkKKvkSyj9D2pALjkL4an9Wtj8rumEm Afz8gUZmvDO6twtiOk+vFTceFCx3P0ELGRY3TKaIEF3VHyME8r4cUeqH06H9anFAPahj 6W8ku57LQ2FJi3mUnE23KsjGUKQMXho4VX8W4= Date: Fri, 1 May 2009 15:31:48 +0200 From: Frederic Weisbecker To: Ingo Molnar Cc: LKML , Jeff Mahoney , ReiserFS Development List , Chris Mason , Alexander Beregalov , Alessio Igor Bogani , Jonathan Corbet , Alexander Viro Subject: Re: [PATCH 2/6] kill-the-BKL/reiserfs: release the write lock before rescheduling on do_journal_end() Message-ID: <20090501133147.GF6011@nowhere> References: <1241145862-21700-1-git-send-email-fweisbec@gmail.com> <1241145862-21700-3-git-send-email-fweisbec@gmail.com> <20090501070911.GG5983@elte.hu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20090501070911.GG5983@elte.hu> User-Agent: Mutt/1.5.18 (2008-05-17) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, May 01, 2009 at 09:09:11AM +0200, Ingo Molnar wrote: > > * Frederic Weisbecker wrote: > > > When do_journal_end() copies data to the journal blocks buffers in memory, > > it reschedules if needed between each block copied and dirtyfied. > > > > We can also release the write lock at this rescheduling stage, > > like did the bkl implicitly. > > > > [ Impact: release the reiserfs write lock when it is not needed ] > > > > Cc: Jeff Mahoney > > Cc: Chris Mason > > Cc: Alexander Beregalov > > Signed-off-by: Frederic Weisbecker > > --- > > fs/reiserfs/journal.c | 2 ++ > > 1 files changed, 2 insertions(+), 0 deletions(-) > > > > diff --git a/fs/reiserfs/journal.c b/fs/reiserfs/journal.c > > index 7976d7d..373d080 100644 > > --- a/fs/reiserfs/journal.c > > +++ b/fs/reiserfs/journal.c > > @@ -4232,7 +4232,9 @@ static int do_journal_end(struct reiserfs_transaction_handle *th, > > next = cn->next; > > free_cnode(sb, cn); > > cn = next; > > + reiserfs_write_unlock(sb); > > cond_resched(); > > + reiserfs_write_lock(sb); > > There's 8 cond_resched()'s in the code - i'd suggest to introduce a > helper for this - reiserfs_write_cond_resched(sb) or so? > > Ingo Indeed, that + the pattern suggested by Al. Thanks.