linux-kernel - Re: vmstat: use our own timer events

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: <Pine.LNX.4.64.0704301041230.6343@schroedinger.engr.sgi.com>
Date:	Mon, 30 Apr 2007 10:42:07 -0700 (PDT)
From:	Christoph Lameter <clameter@....com>
To:	Arjan van de Ven <arjan@...ux.intel.com>
cc:	Andrew Morton <akpm@...ux-foundation.org>,
	linux-kernel@...r.kernel.org
Subject: Re: vmstat: use our own timer events

On Mon, 30 Apr 2007, Arjan van de Ven wrote:

> > Well the cache_reaper of SLAB hits hard todays anyways. This will help
> > if they switch to slub because the counter consolidation is much lighter
> > weight.
> 
> it's not about the weight. It's about waking up *at all*. I've been working
> really hard to get a system with a reasonable average idle time (600ms+), but
> I obviously had to patch the SLAB reaper to be at a different resolution...

If you use SLUB then its going to be gone.

> > I am fine with delaying this. I just wanted the timer guys to have a chance
> > to shape this a bit. Not sure what they want. What they did to the
> > cache_reaper in 2.6.20/21 is bad.
> 
> HUH? The cache_reaper DID NOT CHANGE with the round_jiffies() change.
> Before it had a 3 jiffies per cpu offset, after it has a 3 jiffies per cpu
> offset.

It seems that it does use round_jiffies_relative() instead?
 
-
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/