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
| ||
|
Date: Mon, 26 Jul 2010 20:00:11 +0800 From: Wu Fengguang <fengguang.wu@...el.com> To: Mel Gorman <mel@....ul.ie> Cc: Andrew Morton <akpm@...ux-foundation.org>, Dave Chinner <david@...morbit.com>, Jan Kara <jack@...e.cz>, Christoph Hellwig <hch@...radead.org>, Chris Mason <chris.mason@...cle.com>, Jens Axboe <jens.axboe@...cle.com>, LKML <linux-kernel@...r.kernel.org>, "linux-fsdevel@...r.kernel.org" <linux-fsdevel@...r.kernel.org>, "linux-mm@...ck.org" <linux-mm@...ck.org> Subject: Re: [PATCH 4/6] writeback: sync expired inodes first in background writeback On Mon, Jul 26, 2010 at 06:57:37PM +0800, Mel Gorman wrote: > On Thu, Jul 22, 2010 at 01:09:32PM +0800, Wu Fengguang wrote: > > A background flush work may run for ever. So it's reasonable for it to > > mimic the kupdate behavior of syncing old/expired inodes first. > > > > The policy is > > - enqueue all newly expired inodes at each queue_io() time > > - retry with halfed expire interval until get some inodes to sync > > > > CC: Jan Kara <jack@...e.cz> > > Signed-off-by: Wu Fengguang <fengguang.wu@...el.com> > > Ok, intuitively this would appear to tie into pageout where we want > older inodes to be cleaned first by background flushers to limit the > number of dirty pages encountered by page reclaim. If this is accurate, > it should be detailed in the changelog. Good suggestion. I'll add these lines: This is to help reduce the number of dirty pages encountered by page reclaim, eg. the pageout() calls. Normally older inodes contain older dirty pages, which are more close to the end of the LRU lists. So syncing older inodes first helps reducing the dirty pages reached by the page reclaim code. 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/
Powered by blists - more mailing lists