linux-kernel - Re: [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-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <871voq6nh6.fsf@basil.nowhere.org>
Date:	Thu, 09 Jul 2009 14:37:57 +0200
From:	Andi Kleen <andi@...stfloor.org>
To:	Artem Bityutskiy <Artem.Bityutskiy@...ia.com>
Cc:	Al Viro <viro@...IV.linux.org.uk>,
	Jens Axboe <jens.axboe@...cle.com>,
	linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v3 00/18] periodic write-back timer optimization

Artem Bityutskiy <Artem.Bityutskiy@...ia.com> writes:

>
> 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.

Is waking up every 5 seconds really a problem?

The normal rule of thumb is iirc that longer sleep times than a few hundred
ms give dimishing returns in terms of power saving.

A simple way might be simple to batch the timer better with other timers.

-Andi


-- 
ak@...ux.intel.com -- Speaking for myself only.
--
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/