Message-id: <52C6F722.3090704@samsung.com>
Date: Fri, 03 Jan 2014 21:45:06 +0400
From: Alexey Perevalov <a.perevalov@samsung.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130623
 Thunderbird/17.0.7
MIME-version: 1.0
To: John Stultz <john.stultz@linaro.org>
Cc: linux-kernel@vger.kernel.org, anton@enomsg.org, kyungmin.park@samsung.com,
        akpm@linux-foundation.org
Subject: Re: [PATCH 0/3] Deferrable timers support for timerfd API
References: <1388687448-12987-1-git-send-email-a.perevalov@samsung.com>
 <52C5F38D.5060201@linaro.org>
In-reply-to: <52C5F38D.5060201@linaro.org>
Content-type: text/plain; charset=ISO-8859-1; format=flowed
Content-transfer-encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1492
Lines: 37

On 01/03/2014 03:17 AM, John Stultz wrote:
> On 01/02/2014 10:30 AM, Alexey Perevalov wrote:
>> This version introduces new clockid (CLOCK_DEFERRABLE) , for timerfd_create, instead of
>> new flag (TFD_TIMER_DEFERRABLE) for timerfd_settime introduced in previous version.
> So why did you make this change?
>
> thanks
> -john
>
>

I looked at alarm timers and found approach of making timer behavior 
persistent per file descriptor is better than
changeable by timerfd_settime. I think "end user wake up from suspend" 
and "don't wake up in idle" is the same thing on the same abstraction level.

Yes Anton's previous  patches worked with CLOCK_MONOTONIC only and I 
didn't intend to use it with CLOCK_REALTIME, cause it's hard to me to 
find such use case.
Another way - it's stay as was Anton's patch, I mean as flag for the 
timerfd_settime, but in original patch set both hrtimer and deferrable 
timers initialized in timerfd_create, I think it's not needed. Also 
ability to change timer behavior looks not good if you couldn't change 
alarm timer behavior, not unified API.

If I'm right, only high resolution timer could be REALTIME, and there is 
no deferrable behavior for hrtimer only for timer_list.


-- 
Best regards,
Alexey Perevalov
--
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/