linux-kernel - Re: [PATCH] proc: Get/set timer slack through /proc

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]

Date:	Fri, 1 Jan 2010 15:14:37 -0800
From:	Arjan van de Ven <arjan@...radead.org>
To:	"Smith, GeoffX" <geoffx.smith@...el.com>
Cc:	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] proc: Get/set timer slack through /proc

On Thu, 31 Dec 2009 13:01:49 -0800
"Smith, GeoffX" <geoffx.smith@...el.com> wrote:

> Subject: Get/set timer_slack_ns through /proc
> 
> This patch makes the timer_slack_ns parameter accessible through
> the /proc system.
> 
> On 9/1/2008, arjan@...ux.intel.com submitted a patch to allow a
> process to set the timer slack value as part of the range timers
> feature.  Further, he noted that "Applications and admins can
> override this [the timer slack value] via the prctl()."
> 
> We have found this feature useful in attempting to reduce system
> wakeups caused by timer interrupts.  But we have also found that
> while applications can set their own timer slack value, there is no
> provision for setting the timer slack for another process -- prctl()
> only operates on the current process.  
> 

this statement is incorrect btw;
timerslack is explicitly inherited over exec, so you can have (and we
do have) a utility similar to the nice program, that launches an
application with a specific timer slack.


-- 
Arjan van de Ven 	Intel Open Source Technology Centre
For development, discussion and tips for power savings, 
visit http://www.lesswatts.org
--
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/