linux-kernel - [PATCH 0/6] writeback: moving expire targets for background/kupdate works v2

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-next>] [day] [month] [year] [list]

Message-Id: <20110420080336.441157866@intel.com>
Date:	Wed, 20 Apr 2011 16:03:36 +0800
From:	Wu Fengguang <fengguang.wu@...el.com>
To:	Andrew Morton <akpm@...ux-foundation.org>
Cc:	Wu Fengguang <fengguang.wu@...el.com>,
	LKML <linux-kernel@...r.kernel.org>
Subject: [PATCH 0/6] writeback: moving expire targets for background/kupdate works v2

Andrew,

This aims to reduce possible pageout() calls by making the flusher
concentrate a bit more on old/expired dirty inodes.

Rationals and benchmark numbers are added in patches 05, 06.

It runs fine on simple workloads over ext3/4, xfs, btrfs and NFS.

code refactor
	[PATCH 1/6] writeback: pass writeback_control down to move_expired_inodes()

loop condition fixes
	[PATCH 2/6] writeback: introduce writeback_control.inodes_cleaned
	[PATCH 3/6] writeback: try more writeback as long as something was written

make dirty expire time a moving target
	[PATCH 4/6] writeback: the kupdate expire timestamp should be a moving target
	[PATCH 5/6] writeback: sync expired inodes first in background writeback

consistent requeue policy
it's not an integral part of this patchset, however do depends on patch 03
	[PATCH 6/6] writeback: refill b_io iff empty


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/