From: Dmitry Antipov <dmitry.antipov@linaro.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Thomas Gleixner <tglx@linutronix.de>,
linux-kernel@vger.kernel.org, linaro-dev@lists.linaro.org,
patches@linaro.org, linux-man@vger.kernel.org
Subject: Re: [RFC PATCH] hrtimers: system-wide and per-task hrtimer slacks
Date: Fri, 06 Apr 2012 13:14:46 +0400 [thread overview]
Message-ID: <4F7EB406.5020703@linaro.org> (raw)
In-Reply-To: <20120404171013.ac08575d.akpm@linux-foundation.org>
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 seems you're looking at the previous version of this patch
(http://lkml.org/lkml/2012/2/20/55). Latest proposal is
http://lwn.net/Articles/484162/, which defines PR_SET_TIMERSLACK
action as:
...
case PR_SET_TIMERSLACK:
if (arg2 <= 0)
current->timer_slack_ns =
default_timer_slack_ns;
else if (arg2 <= HRTIMER_MAX_SLACK)
current->timer_slack_ns = arg2;
else
error = -EINVAL;
break;
...
> If we do make changes in this area then the prctl manpage should be
> updated, please. And if
> http://www.spinics.net/lists/linux-man/msg01149.html represents the
> current state of that manpage then it should be updated anyway - that
> entry doesn't say anything about the (arg2<= 0) case.
I sent a patch for man pages too, it should be one of the recent posts
at http://www.spinics.net/lists/linux-man/index.html.
Dmitry
next prev parent reply other threads:[~2012-04-06 9:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-20 7:49 [RFC PATCH] hrtimers: system-wide and per-task hrtimer slacks Dmitry Antipov
2012-04-05 0:10 ` Andrew Morton
2012-04-06 9:14 ` Dmitry Antipov [this message]
2012-04-24 22:06 ` Michael Kerrisk
-- strict thread matches above, loose matches on Subject: below --
2012-02-28 8:46 Dmitry Antipov
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=4F7EB406.5020703@linaro.org \
--to=dmitry.antipov@linaro.org \
--cc=akpm@linux-foundation.org \
--cc=linaro-dev@lists.linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-man@vger.kernel.org \
--cc=patches@linaro.org \
--cc=tglx@linutronix.de \
/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;
as well as URLs for NNTP newsgroup(s).