From: "Smith, GeoffX" <geoffx.smith@intel.com>
To: Arjan van de Ven <arjan@infradead.org>
CC: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Date: Mon, 4 Jan 2010 09:29:21 -0800
Subject: RE: [PATCH] proc: Get/set timer slack through /proc
Thread-Topic: [PATCH] proc: Get/set timer slack through /proc
Thread-Index: AcqLN9oGLR0i9eaOShOvycGHL2kqwACJANWQ
Message-ID: <354B2877CF17F44BB3FA44EB4DB0E5470C91CE1DE7@orsmsx510.amr.corp.intel.com>
References: <354B2877CF17F44BB3FA44EB4DB0E5470C91CE1D19@orsmsx510.amr.corp.intel.com>
 <20100101151437.17834b25@infradead.org>
In-Reply-To: <20100101151437.17834b25@infradead.org>
Accept-Language: en-US
Content-Language: en-US
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 8BIT
MIME-Version: 1.0
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1653
Lines: 37


On Friday, January 01, 2010, Arjan@infradead.org wrote:

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

Hmmm, that seems a lot less flexible, but I see how that would work.

Nonetheless, using "nice" as a model is that you would have to modify anything that launches applications, right?  This would mean modifying /etc/init.d and application scripts, which seems beyond the scope of "admin".   Or am I missing something?


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/