| 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
| ||
|
Message-Id: <20120228140022.614718843@intel.com> Date: Tue, 28 Feb 2012 22:00:22 +0800 From: Fengguang Wu <fengguang.wu@...el.com> To: Andrew Morton <akpm@...ux-foundation.org> Cc: Fengguang Wu <fengguang.wu@...el.com>, LKML <linux-kernel@...r.kernel.org> Subject: [PATCH 0/9] [RFC] pageout work and dirty reclaim throttling Andrew, This aims to improve two major page reclaim problems a) pageout I/O efficiency, by sending pageout work to the flusher b) interactive performance, by selectively throttle the writing tasks when under heavy pressure of dirty/writeback pages. The tests results for 1) and 2) look promising and are included in patches 6 and 9. However there are still two open problems. 1) ext4 "hung task" problem, as put by Jan Kara: : We enter memcg reclaim from grab_cache_page_write_begin() and are : waiting in reclaim_wait(). Because grab_cache_page_write_begin() is : called with transaction started, this blocks transaction from : committing and subsequently blocks all other activity on the : filesystem. The fact is this isn't new with your patches, just your : changes or the fact that we are running in a memory constrained cgroup : make this more visible. 2) the pageout work may be deferred by sync work Like 1), there is also no obvious good way out. The closest fix may be to service some pageout works each time the other work finishes with one inode. But problem is, the sync work does not limit chunk size at all. So it's possible for sync to work on one inode for 1 minute before giving the pageout works a chance... Due to problems (1) and (2), it's still not a complete solution. For ease of debug, several trace_printk() and debugfs interfaces are included for now. [PATCH 1/9] memcg: add page_cgroup flags for dirty page tracking [PATCH 2/9] memcg: add dirty page accounting infrastructure [PATCH 3/9] memcg: add kernel calls for memcg dirty page stats [PATCH 4/9] memcg: dirty page accounting support routines [PATCH 5/9] writeback: introduce the pageout work [PATCH 6/9] vmscan: dirty reclaim throttling [PATCH 7/9] mm: pass __GFP_WRITE to memcg charge and reclaim routines [PATCH 8/9] mm: dont set __GFP_WRITE on ramfs/sysfs writes [PATCH 9/9] mm: debug vmscan waits fs/fs-writeback.c | 230 +++++++++++++++++++++- fs/nfs/write.c | 4 fs/super.c | 1 include/linux/backing-dev.h | 2 include/linux/gfp.h | 2 include/linux/memcontrol.h | 13 + include/linux/mmzone.h | 1 include/linux/page_cgroup.h | 23 ++ include/linux/sched.h | 1 include/linux/writeback.h | 18 + include/trace/events/vmscan.h | 68 ++++++ include/trace/events/writeback.h | 12 - mm/backing-dev.c | 10 mm/filemap.c | 20 + mm/internal.h | 7 mm/memcontrol.c | 199 ++++++++++++++++++- mm/migrate.c | 3 mm/page-writeback.c | 6 mm/page_alloc.c | 1 mm/swap.c | 4 mm/truncate.c | 1 mm/vmscan.c | 298 ++++++++++++++++++++++++++--- 22 files changed, 864 insertions(+), 60 deletions(-) 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