mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Arjan van de Ven <arjan@infradead.org>
To: "Smith, GeoffX" <geoffx.smith@intel.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] proc: Get/set timer slack through /proc
Date: Fri, 1 Jan 2010 15:14:37 -0800	[thread overview]
Message-ID: <20100101151437.17834b25@infradead.org> (raw)
In-Reply-To: <354B2877CF17F44BB3FA44EB4DB0E5470C91CE1D19@orsmsx510.amr.corp.intel.com>

On Thu, 31 Dec 2009 13:01:49 -0800
"Smith, GeoffX" <geoffx.smith@intel.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@linux.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

  reply	other threads:[~2010-01-01 23:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-31 21:01 Smith, GeoffX
2010-01-01 23:14 ` Arjan van de Ven [this message]
2010-01-04 17:29   ` Smith, GeoffX

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20100101151437.17834b25@infradead.org \
    --to=arjan@infradead.org \
    --cc=geoffx.smith@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®