linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Fengguang Wu <fengguang.wu@intel.com>
To: Jan Kara <jack@suse.cz>
Cc: linux-fsdevel@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] writeback: Do not sort b_io list only because of block device inode
Date: Tue, 9 Jul 2013 22:32:17 +0800	[thread overview]
Message-ID: <20130709143217.GA6944@localhost> (raw)
In-Reply-To: <20130708160602.GA14739@quack.suse.cz>

On Mon, Jul 08, 2013 at 06:06:02PM +0200, Jan Kara wrote:
> On Mon 24-06-13 10:07:49, Jan Kara wrote:
> > It is very likely that block device inode will be part of BDI dirty list
> > as well. However it doesn't make sence to sort inodes on the b_io list
> > just because of this inode (as it contains buffers all over the device
> > anyway). So save some CPU cycles which is valuable since we hold relatively
> > contented wb->list_lock.
>   Ping? Fengguang, can you merge the patch please?

OK! It's a good optimization to have.

Thanks,
Fengguang

      reply	other threads:[~2013-07-09 14:32 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-24  8:07 [PATCH] writeback: Do not sort b_io list only because of block device inode Jan Kara
2013-07-08 16:06 ` Jan Kara
2013-07-09 14:32   ` Fengguang Wu [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=20130709143217.GA6944@localhost \
    --to=fengguang.wu@intel.com \
    --cc=jack@suse.cz \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).