linux-kernel - Re: 2.6.19 -mm merge plans

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: <20060923110749.GC20778@elf.ucw.cz>
Date:	Sat, 23 Sep 2006 13:07:49 +0200
From:	Pavel Machek <pavel@....cz>
To:	Ingo Molnar <mingo@...e.hu>
Cc:	Andrew Morton <akpm@...l.org>, linux-kernel@...r.kernel.org,
	Thomas Gleixner <tglx@...utronix.de>,
	John Stultz <johnstul@...ibm.com>,
	Arjan van de Ven <arjan@...radead.org>
Subject: Re: 2.6.19 -mm merge plans

Hi!

> > > would be nice to merge the -hrt queue that goes right ontop this 
> > > queue. Even if HIGH_RES_TIMERS is "default n" in the beginning. That 
> > > gives us high-res timers and dynticks which are both very important 
> > > features to certain classes of users/devices.
> > 
> > dynticks give benefit of 0.3W, or 20minutes (IIRC) from 8hours on 
> > thinkpad x60... and they were around for way too long. (When baseline 
> > is hz=250, it is 0.5W from hz=1000 baseline). It would be cool to 
> > finally merge them.
> 
> note that this is a new implementation of dynticks though, not Con's 
> older stuff which you probably used, right? But it's fairly low-impact 

(Well, I cheated, and just measured difference between HZ=100 and
HZ=250/1000. Dynticks should be even slightly better than that.)
								Pavel

-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
-
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/