| 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: <20070810063412.238042387@mail.ustc.edu.cn> Date: Fri, 10 Aug 2007 14:34:12 +0800 From: Fengguang Wu <wfg@...l.ustc.edu.cn> To: Andrew Morton <akpm@...l.org> Cc: linux-fsdevel@...r.kernel.org Subject: [PATCH 0/4] [RFC][PATCH] fs-writeback: redefining the dirty inode queues Andrew, I'd like to propose a cleaner way of using the s_dirty, s_io, s_more_io queues for the writeback of dirty inodes. The basic idea is to clearly define the function of the queues, especially to decouple s_diry from s_io/s_more_io. The details are in the changelog of patch 2. The patches are some cleanups on top of Andrew's s_dirty time-ordering patches and Ken's s_more_io patch: [PATCH 1/4] writeback: check time-ordering of s_io and s_more_io [PATCH 2/4] writeback: 3-queue based writeback schedule [PATCH 3/4] writeback: function renames and cleanups [PATCH 4/4] writeback: fix ntfs with sb_has_dirty_inodes() fs/fs-writeback.c | 196 +++++++++++++++++++++++-------------------- fs/ntfs/super.c | 4 include/linux/fs.h | 1 3 files changed, 108 insertions(+), 93 deletions(-) Note that the patches need rework for inserting into the right place of your queue of -mm patches. I'll take care of it in the next take. Thank you, 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