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: <20080329212203.GB2153@elf.ucw.cz>
Date:	Sat, 29 Mar 2008 22:22:03 +0100
From:	Pavel Machek <pavel@....cz>
To:	Michael Meyer <mike65134@...oo.de>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: performance differences: "maxcpus=1" vs. "echo 0 >
	/sys/devices/system/cpu/cpu1/online"

Hi!

> > > what is the difference between booting a dual core
> > > machine with "maxcpus=1" or by deactivating the second
> > > core at run time with "echo 0 >
> > > /sys/devices/system/cpu/cpu1/online"?
> > 
> > maxcpus=1 : core stays powered off
> > 0 > online : core enters halt.
> > 
> > > I observed a funny behaviour of apache ant: although
> > > it uses javac which is single threaded, a compile run
> > > with "maxcpus=1" is actually faster than a compile run
> > > with both cores activated. But with the second core
> > > deactivated using "echo 0 >
> > > /sys/devices/system/cpu/cpu1/online" it is even slower
> > > than with both cores.
> > 
> > Thermal fun? Check cooling.
> 
> I have an extremely well cooled case and a Thermaltake Typhoon sitting
> on the E6600 (Intel TDP 65 Watt). At a room temperature of 20°C both
> cores idle at 21°C and after one hour of two instances of prime95
> running they are both at 28-33°C. As the E6600 is specified until 60°C
> (I believe), this should prevent any thermal throttling?

Ok, and your chip is too old to have "Enhanced Dynamic Acceleration
Technology" (Intel, can't you use some reasonable names?!)... both
would explain effects you see, and it is neither...

You could try implementing deep sleep (C4) state for cpu hotplug....
									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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ