From: "Carlos O'Donell" <carlos@redhat.com>
To: Thomas Gleixner <tglx@linutronix.de>,
Daniel Church <dchurch@andplus.com>
Cc: linux-kernel@vger.kernel.org, libc-alpha@sourceware.org
Subject: Re: [PATCH v2 2/2] posix-timers: Exposes DELAYTIMER_MAX constant used to govern overruns
Date: Sat, 24 Jan 2015 14:36:21 -0500 [thread overview]
Message-ID: <54C3F435.3070505@redhat.com> (raw)
In-Reply-To: <alpine.DEB.2.11.1501242015260.5526@nanos>
On 01/24/2015 02:20 PM, Thomas Gleixner wrote:
> On Sat, 24 Jan 2015, Daniel Church wrote:
>
>> POSIX.1-2001 specification of timer_getoverrun() supports constant
>> DELAYTIMER_MAX which prevents overflow and caps overrun count. Exposes
>> delaytimer_max value to userland via /proc/sys/kernel/delaytimer_max such
>
> I know that you try to match the posix name, but when looking at the
> prctl w/o knowing about DELAYTIMER_MAX, it's non intuitive.
>
> Something like posixtimer_max_overruns or if you insist on the
> delaytimer_max part, then let us prepend it with posixtimer_ at least.
>
> New prctls require an update of Documentation/sysctl/kernel.txt.
Agreed, the name should be self-explanatory and point at POSIX.
The documentation should be detailed and explain exactly what this
is for, what are valid values, and why you would ever want to change
them.
Cheers,
Carlos.
prev parent reply other threads:[~2015-01-24 19:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <[PATCH 0/2] posix-timers: Prevents overrun counter overflow, adds DELAYTIMER_MAX>
2015-01-24 17:48 ` [PATCH v2 0/2] posix-timers: Prevents overrun counter overflow, adds DELAYTIMER_MAX Daniel Church
2015-01-24 17:48 ` [PATCH v2 1/2] posix-timers: Prevents overrun counter overflow Daniel Church
2015-01-24 18:17 ` Richard Cochran
2015-01-24 19:14 ` Thomas Gleixner
2015-01-24 19:37 ` Carlos O'Donell
2015-01-24 17:48 ` [PATCH v2 2/2] posix-timers: Exposes DELAYTIMER_MAX constant used to govern overruns Daniel Church
2015-01-24 19:20 ` Thomas Gleixner
2015-01-24 19:36 ` Carlos O'Donell [this message]
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=54C3F435.3070505@redhat.com \
--to=carlos@redhat.com \
--cc=dchurch@andplus.com \
--cc=libc-alpha@sourceware.org \
--cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.