From: akpm@linux-foundation.org
To: mm-commits@vger.kernel.org
Cc: bfields@citi.umich.edu, tglx@linutronix.de
Subject: + timersc-document-meaning-of-deferrable-timer.patch added to -mm tree
Date: Thu, 08 Jul 2010 15:19:46 -0700 [thread overview]
Message-ID: <201007082219.o68MJkw8032379@imap1.linux-foundation.org> (raw)
The patch titled
timers.c: document meaning of deferrable timer
has been added to the -mm tree. Its filename is
timersc-document-meaning-of-deferrable-timer.patch
Before you just go and hit "reply", please:
a) Consider who else should be cc'ed
b) Prefer to cc a suitable mailing list as well
c) Ideally: find the original patch on the mailing list and do a
reply-to-all to that, adding suitable additional cc's
*** Remember to use Documentation/SubmitChecklist when testing your code ***
See http://userweb.kernel.org/~akpm/stuff/added-to-mm.txt to find
out what to do about this
The current -mm tree may be found at http://userweb.kernel.org/~akpm/mmotm/
------------------------------------------------------
Subject: timers.c: document meaning of deferrable timer
From: J. Bruce Fields <bfields@citi.umich.edu>
Steal some text from 6e453a67510 "Add support for deferrable timers". A
reader shouldn't have to dig through the git logs for the basic
description of a deferrable timer.
Signed-off-by: J. Bruce Fields <bfields@citi.umich.edu>
Cc: Thomas Gleixner <tglx@linutronix.de>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
kernel/timer.c | 9 +++++++--
1 file changed, 7 insertions(+), 2 deletions(-)
diff -puN kernel/timer.c~timersc-document-meaning-of-deferrable-timer kernel/timer.c
--- a/kernel/timer.c~timersc-document-meaning-of-deferrable-timer
+++ a/kernel/timer.c
@@ -90,8 +90,13 @@ static DEFINE_PER_CPU(struct tvec_base *
/*
* Note that all tvec_bases are 2 byte aligned and lower bit of
- * base in timer_list is guaranteed to be zero. Use the LSB for
- * the new flag to indicate whether the timer is deferrable
+ * base in timer_list is guaranteed to be zero. Use the LSB to
+ * indicate whether the timer is deferrable.
+ *
+ * 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.
*/
#define TBASE_DEFERRABLE_FLAG (0x1)
_
Patches currently in -mm which might be from bfields@citi.umich.edu are
linux-next.patch
timersc-document-meaning-of-deferrable-timer.patch
reiser4.patch
reply other threads:[~2010-07-08 22:19 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=201007082219.o68MJkw8032379@imap1.linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=bfields@citi.umich.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=mm-commits@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