From: Anton Vorontsov <cbouatmailru@gmail.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: "Pekka Enberg" <penberg@kernel.org>,
"Leonid Moiseichuk" <leonid.moiseichuk@nokia.com>,
"Bartlomiej Zolnierkiewicz" <b.zolnierkie@samsung.com>,
"Colin Cross" <ccross@android.com>,
"Arve Hjønnevåg" <arve@android.com>,
"Davide Libenzi" <davidel@xmailserver.org>,
"Andrew Morton" <akpm@linux-foundation.org>,
"Ingo Molnar" <mingo@elte.hu>,
"John Stultz" <john.stultz@linaro.org>,
linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org,
linaro-kernel@lists.linaro.org, patches@linaro.org,
kernel-team@android.com
Subject: Re: [PATCH/RFC 0/4] Deferrable timers support for timerfd API
Date: Sun, 16 Sep 2012 22:53:07 -0700 [thread overview]
Message-ID: <20120917055306.GA29081@lizard> (raw)
In-Reply-To: <20120902054335.GA12741@lizard>
Hi all,
On Sat, Sep 01, 2012 at 10:43:35PM -0700, Anton Vorontsov wrote:
> This patch set implements a userland-side API for generic deferrable
> timers, per linux/timer.h:
>
> * A deferrable timer will work normally when the system is busy, but
> * will not cause a CPU to come out of idle just to service it; instead,
> * the timer will be serviced when the CPU eventually wakes up with a
> * subsequent non-deferrable timer.
>
> These timers are crucial for power saving, i.e. periodic tasks that want
> to work in background when the system is under use, but don't want to
> cause wakeups themselves.
Just a friendly ping. Does anyone had a chance to look into this,
whether the idea bad or good, or whether the implementation is OK?
Thanks!
Anton.
prev parent reply other threads:[~2012-09-17 5:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-02 5:43 [PATCH/RFC 0/4] Deferrable timers support for timerfd API Anton Vorontsov
2012-09-02 5:45 ` [PATCH 1/4] kernel/time: Add new helpers to convert ktime to/from jiffies Anton Vorontsov
2012-09-02 5:45 ` [PATCH 2/4] timerfd: Move repeated logic into timefd_rearm() Anton Vorontsov
2012-09-02 5:45 ` [PATCH 3/4] timerfd: Factor out timer-type unspecific timerfd_expire() Anton Vorontsov
2012-09-02 5:45 ` [PATCH 4/4] timerfd: Add support for deferrable timers Anton Vorontsov
2012-09-17 5:53 ` Anton Vorontsov [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=20120917055306.GA29081@lizard \
--to=cbouatmailru@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=arve@android.com \
--cc=b.zolnierkie@samsung.com \
--cc=ccross@android.com \
--cc=davidel@xmailserver.org \
--cc=john.stultz@linaro.org \
--cc=kernel-team@android.com \
--cc=leonid.moiseichuk@nokia.com \
--cc=linaro-kernel@lists.linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=patches@linaro.org \
--cc=penberg@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.