linux-kernel - Re: [PATCH] writeback: Do not sort b_io list only because of block device inode

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20130709143217.GA6944@localhost>
Date:	Tue, 9 Jul 2013 22:32:17 +0800
From:	Fengguang Wu <fengguang.wu@...el.com>
To:	Jan Kara <jack@...e.cz>
Cc:	linux-fsdevel@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] writeback: Do not sort b_io list only because of block
 device inode

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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/