linux-kernel - [PATCH v2 0/4] do not use s

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]

Date:	Mon,  2 Apr 2012 14:45:35 +0300
From:	Artem Bityutskiy <artem.bityutskiy@...ux.intel.com>
To:	Ted Tso <tytso@....edu>
Cc:	Linux Kernel Maling List <linux-kernel@...r.kernel.org>,
	Linux FS Maling List <linux-fsdevel@...r.kernel.org>,
	Ext4 Mailing List <linux-ext4@...r.kernel.org>,
	Jan Kara <jack@...e.cz>
Subject: [PATCH v2 0/4] do not use s_dirt in ext4

This patch-set makes ext4 independent of the VFS superblock management
services. Namely, ext4 does not require to register the 'write_super()' VFS
call-back.

The reason of this exercises is to get rid of the 'sync_supers()' kernel thread
which wakes up every 5 seconds (by default) even if all superblocks are clean.
This is wasteful from power management POW (unnecessary wake-ups).

Version 1 of this patch-set can be found here:
https://lkml.org/lkml/2012/3/20/220

Changes between v1 and v2.
  * Rake different strategy - instead of pushing 's_dirt' down "as-is" and
    emulating old behavior, we now just submit the superblock for writing
    straight away, either via the journal or directly. Thank to Jan Kara
    for helping with this.
  * Ted picked some of the patches already, which made this series shorter
    - thanks!
  * This time I've tested the changes using xfstests.
  * Rebased to 3.4-rc1.

Note: Ted, you merged the "mm: export dirty_writeback_interval", but it looks
like we won't need this for ext[23]. However, for other file-systems we will
need this change.

Thanks,
Artem.
--
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/