linux-kernel - [PATCH v3 00/18] periodic write-back timer optimization

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:	Thu, 09 Jul 2009 11:48:22 +0300
From:	Artem Bityutskiy <Artem.Bityutskiy@...ia.com>
To:	Al Viro <viro@...IV.linux.org.uk>,
	Jens Axboe <jens.axboe@...cle.com>
Cc:	linux-fsdevel@...r.kernel.org,
	Artem Bityutskiy <Artem.Bityutskiy@...ia.com>,
	linux-kernel@...r.kernel.org
Subject: [PATCH v3 00/18] periodic write-back timer optimization

Hi Al, Jens,

this is the third or fourth attempt. Al, would you please take a look
at this? Would it be possible to get your ack and then merge this
via Jens' tree?

The patches attempt to optimize the periodic write-back and stop it when
there are no dirty data. IOW, we do not want the thread to wake up every
5 seconds (by default), find there is nothing to do, and so on. We want
to save power instead.

The patches are against Jens Axboe's per-bdi write-back tree. Namely,
against:

git://git.kernel.dk/linux-2.6-block.git writeback-v12

Patches 01-16 introduce 2 VFS helpers and wrap all 'sb->s_dirt'
manipulations.

Patch 17 re-names s_dirt to s_dirty in order to make sure we catch
all direct s_dirt accesses.

Patch 18 optimizes the periodic 'sync_supers' thread. This used
to be 'pdflush', but Jens re-worked this area and now it is called
'sync_supers'. By the way, with Jens' changes the former kupdated stuff
stuff looks a lot cleaner and it is easier to work on top of that.

-- 
Best Regards,
Artem Bityutskiy (Артём Битюцкий)
--
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/