Dmitry,
On Fri, Apr 6, 2012 at 9:14 PM, Dmitry Antipov
wrote:
> On 04/05/2012 04:10 AM, Andrew Morton wrote:
>
>> Well.. there are some back-incompatibilities here.
>> prctl(PR_SET_TIMERSLACK, -1) used to restore current's slack setting to
>> whatever-we-inherited-at-fork, but that has been remo
On 04/05/2012 04:10 AM, Andrew Morton wrote:
Well.. there are some back-incompatibilities here.
prctl(PR_SET_TIMERSLACK, -1) used to restore current's slack setting to
whatever-we-inherited-at-fork, but that has been removed. What are the
implications of this, and did we need to do it?
It se
On Mon, 20 Feb 2012 11:49:32 +0400
Dmitry Antipov wrote:
> This patch proposes a system-wide sysctl-aware default for the
> high-resolution timer slack value, which may be changed from 0
> to HRTIMER_MAX_SLACK nanoseconds. Default system-wide and per-task
> values are HRTIMER_DEFAULT_SLACK. Per-t