mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alexey Perevalov <a.perevalov@samsung.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: John Stultz <john.stultz@linaro.org>,
	linux-kernel@vger.kernel.org, anton@enomsg.org,
	kyungmin.park@samsung.com, akpm@linux-foundation.org,
	cw00.choi@samsung.com, Alexey Perevalov <a.perevalov@samsung.com>
Subject: Re: [PATCH v2 0/3] Deferrable timers support for timerfd API
Date: Mon, 27 Jan 2014 11:12:24 +0400	[thread overview]
Message-ID: <52E606D8.6000401@samsung.com> (raw)
In-Reply-To: <52DEC6A3.9020600@linaro.org>

Dear Thomas,
could you please comment John's question (see bellow) regarding flags.

On 01/21/2014 11:12 PM, John Stultz wrote:
> On 01/13/2014 02:43 AM, Alexey Perevalov wrote:
>> Hello dear community.
>>
>> This is reworked patch set of original Anton's Vorontsov
>> proposal regarding unified deferrable timers in the user space.
>> http://lwn.net/Articles/514707/
>>
>>
>> I decided to resubmit it due we found it usefull for us too.
>>
>> timerfd was modified since Anton's commit, Alarm support was added.
>> This isn't only rebase. Anton's previous version used deferrable timer
>> in couple with hrtimer. This version uses only deferrable timer. It
>> mean the behaviour of overrun number is different.
>> e.g. if you don't poll one second timer for a 10 seconds - you'll get
>> 10 overruns with hrtimer, but for deferrable timer it could be another value.
>>
> Sorry, last week was a little crazy and I didn't get a chance to closely
> review this. But looking at this my major conceptual objection with the
> previous patchset (introducing the new clockid) is gone.
>
> My remaining conceptual concern here is that the TIMER_DEFERRABLE flag
> is a timerfd only construct here, and I worry we should make sure we
> think this through well enough that the same functionality can be
> supported via other timer interfaces (like clock_nanosleep, etc), which
> may mean the functionality should be pushed more deeply into the hrtimer
> subsystem.
>
> So main suggestion here is to make sure you cc Thomas Gleixner on future
> iterations, so he can provide some thoughts on what the best approach
> might be here. I know he also has some plans that might collide with the
> jiffies_to_ktime work.
>
> Thomas: Any thought here? Should we be trying to unify the timerfd flags
> and the posix timer flags (specifically things like TIMER_CANCEL_ON_SET,
> which is currently timerfd-only)?  Should a deferrable flag be added to
> the hrtimer core or left to the timer wheel?
>
> thanks
> -john
>


-- 
Best regards,
Alexey Perevalov

  reply	other threads:[~2014-01-27  7:12 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-13 10:43 Alexey Perevalov
2014-01-13 10:43 ` [PATCH v2 1/3] kernel/time: Add new helpers to convert ktime to/from jiffies Alexey Perevalov
2014-01-14  0:15   ` Chanwoo Choi
2014-01-13 10:43 ` [PATCH v2 2/3] timerfd: Factor out timer-type unspecific timerfd_expire() Alexey Perevalov
2014-01-13 10:43 ` [PATCH v2 3/3] timerfd: Add support for deferrable timers Alexey Perevalov
2014-01-13 15:30 ` [PATCH v2 0/3] Deferrable timers support for timerfd API Alexey Perevalov
2014-01-13 17:36   ` Andi Kleen
2014-01-14  6:44     ` Alexey Perevalov
2014-01-21 19:12 ` John Stultz
2014-01-27  7:12   ` Alexey Perevalov [this message]
2014-02-04 16:10     ` Thomas Gleixner
2014-02-05  6:43       ` Alexey Perevalov
2014-02-05 21:41         ` Thomas Gleixner
2014-02-05 22:02           ` John Stultz
2014-02-05 22:16             ` Thomas Gleixner
2014-02-06 17:38               ` Alexey Perevalov
2014-02-06 17:47                 ` John Stultz
2014-02-06 20:50                 ` Thomas Gleixner
2014-02-07 17:41                   ` Alexey Perevalov
2014-02-16 15:20                   ` Alexey Perevalov
2014-02-16 15:39                     ` Thomas Gleixner
2014-02-17 14:15                       ` Alexey Perevalov
2014-02-18 19:43                         ` Thomas Gleixner
2014-02-18 19:48                       ` Alexey Perevalov
2014-02-18 22:33                         ` Thomas Gleixner
2014-02-19  7:08                           ` Alexey Perevalov
2014-02-03  6:54   ` Alexey Perevalov
2014-02-03 23:58     ` John Stultz

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=52E606D8.6000401@samsung.com \
    --to=a.perevalov@samsung.com \
    --cc=akpm@linux-foundation.org \
    --cc=anton@enomsg.org \
    --cc=cw00.choi@samsung.com \
    --cc=john.stultz@linaro.org \
    --cc=kyungmin.park@samsung.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

Powered by JetHome