linux-kernel - Re: high power consumption in recent kernels

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: <1284689374.17745.89.camel@debian>
Date:	Fri, 17 Sep 2010 10:09:34 +0800
From:	"Alex,Shi" <alex.shi@...el.com>
To:	Norbert Preining <preining@...ic.at>
Cc:	Peter Zijlstra <peterz@...radead.org>,
	"Chen, Tim C" <tim.c.chen@...el.com>,
	"arjan@...radead.org" <arjan@...radead.org>,
	"efault@....de" <efault@....de>,
	"Li, Shaohua" <shaohua.li@...el.com>, tglx <tglx@...utronix.de>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: high power consumption in recent kernels

> > - how to reduce the "extra timer interrupt"?
> The timer was listed in /proc/timer_stats, you can post its contents,
> and let's see what is abnormal here. 
> 
Norbert, did you try the patch? 
We are still thinking the too many "extra timer interrupts" on your
system, maybe the following message can give some help. So, could you
like to check if your system is using pit timer? 
#cat /proc/timer_list
Or some APP/system services in your system is using lots of timer? 

===
http://www.linuxpowertop.org/faq.php 

Even with a tickless kernel, there are some timer ticks still happening:

1.) For userspace events (also shown in the lower "top 10 events" list).
2.) The kernel still has timer ticks when userspace is executing code,
to sample and get data for the "top" program.
3.) Hardware timers have a maximum time they can be set for, for the PIT
timer (the one used if you don't have HPET active). This is around 27
milliseconds. If you would have longer sleep times than the maximum, the
kernel has no choice but to set the timer to the maximum repeatedly
until the actual event is approaching.

The "extra timer interrupts" data is a combination fo 1 and 3.

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