All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mingming Cao <cmm@us.ibm.com>
To: Jan Kara <jack@suse.cz>
Cc: Eric Sandeen <sandeen@redhat.com>,
	"Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>,
	tytso@mit.edu, linux-ext4@vger.kernel.org
Subject: Re: [PATCH] jbd2: We shouldnot cap writeback when we are doing a journal commit
Date: Fri, 27 Jun 2008 16:52:28 -0700	[thread overview]
Message-ID: <1214610748.6837.20.camel@mingming-laptop> (raw)
In-Reply-To: <20080627210439.GA15342@duck.suse.cz>

I fold this change to the parent patch: delalloc-new-ordered-mode.patch
in patch queue

Mingming
On Fri, 2008-06-27 at 23:04 +0200, Jan Kara wrote:
> On Fri 27-06-08 13:11:25, Eric Sandeen wrote:
> > Aneesh Kumar K.V wrote:
> > > A journal commit need to make sure we submit data buffers before
> > > we submit the meta-data buffers in ordered mode. We should
> > > not be looking at BDI_CAP_NO_WRITEBACK when doing a journal commit.
> > > 
> > > Signed-off-by: Aneesh Kumar K.V <aneesh.kumar@linux.vnet.ibm.com>
> > 
> > and I don't think we'll ever even see that flag set...
> > 
> > Acked-by: Eric Sandeen <sandeen@redhat.com>
>   Yes, I also don't think it really matters :). So feel free to remove that
> check.
> 
> 								Honza
> > 
> > > ---
> > >  fs/jbd2/commit.c |    3 ---
> > >  1 files changed, 0 insertions(+), 3 deletions(-)
> > > 
> > > diff --git a/fs/jbd2/commit.c b/fs/jbd2/commit.c
> > > index 32ca3c3..f8b3be8 100644
> > > --- a/fs/jbd2/commit.c
> > > +++ b/fs/jbd2/commit.c
> > > @@ -203,9 +203,6 @@ static int journal_submit_inode_data_buffers(struct address_space *mapping)
> > >  		.for_writepages = 1,
> > >  	};
> > >  
> > > -	if (!mapping_cap_writeback_dirty(mapping))
> > > -		return 0;
> > > -
> > >  	ret = generic_writepages(mapping, &wbc);
> > >  	return ret;
> > >  }
> > 


      reply	other threads:[~2008-06-27 23:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-27 18:07 [PATCH] jbd2: We shouldnot cap writeback when we are doing a journal commit Aneesh Kumar K.V
2008-06-27 18:11 ` Eric Sandeen
2008-06-27 21:04   ` Jan Kara
2008-06-27 23:52     ` Mingming Cao [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1214610748.6837.20.camel@mingming-laptop \
    --to=cmm@us.ibm.com \
    --cc=aneesh.kumar@linux.vnet.ibm.com \
    --cc=jack@suse.cz \
    --cc=linux-ext4@vger.kernel.org \
    --cc=sandeen@redhat.com \
    --cc=tytso@mit.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.