From: Geoff Gustafson <geoff@linux.jf.intel.com>
To: akpm@osdl.org
Cc: linux-kernel@vger.kernel.org, mingo@elte.hu,
kenneth.w.chen@intel.com, hch@infradead.org
Subject: Re: [RFC] [PATCH] Performance of del_timer_sync
Date: Tue, 11 May 2004 15:46:35 -0700 [thread overview]
Message-ID: <40A157CB.1010100@linux.intel.com> (raw)
Andrew Morton wrote:
> <anal>del_singleshot_timer_sync</anal>
>
> I vote we leave it up to Ken. But please, not del_timer_kenneth().
Despite your markup language, I thought keeping the 'sync' sounded like
a good idea, since that's the function it's replacing.
Here's a patch. I've done a small amount of testing with a 4p machine.
I've at least seen that the average call to singleshot is down around 90
cycles, pretty similar/expected. We'll test on the original platform and
post results.
- Geoff
* I am in a transitional period w/ email clients and can't seem to use
any of them properly. Sorry for the dups, etc.
diff -Naur fresh/fs/aio.c timer/fs/aio.c
--- fresh/fs/aio.c Sun May 9 19:32:29 2004
+++ timer/fs/aio.c Tue May 11 15:14:47 2004
@@ -793,7 +793,7 @@
static inline void clear_timeout(struct timeout *to)
{
- del_timer_sync(&to->timer);
+ del_singleshot_timer_sync(&to->timer);
}
static int read_events(struct kioctx *ctx,
diff -Naur fresh/include/linux/timer.h timer/include/linux/timer.h
--- fresh/include/linux/timer.h Sun May 9 19:32:54 2004
+++ timer/include/linux/timer.h Tue May 11 14:21:36 2004
@@ -88,8 +88,10 @@
#ifdef CONFIG_SMP
extern int del_timer_sync(struct timer_list * timer);
+ extern int del_singleshot_timer_sync(struct timer_list * timer);
#else
# define del_timer_sync(t) del_timer(t)
+# define del_singleshot_timer_sync(t) del_timer(t)
#endif
extern void init_timers(void);
diff -Naur fresh/kernel/timer.c timer/kernel/timer.c
--- fresh/kernel/timer.c Sun May 9 19:33:13 2004
+++ timer/kernel/timer.c Tue May 11 15:08:24 2004
@@ -350,6 +350,35 @@
}
EXPORT_SYMBOL(del_timer_sync);
+
+/***
+ * del_singleshot_timer_sync - deactivate a non-recursive timer
+ * @timer: the timer to be deactivated
+ *
+ * This function is an optimization of del_timer_sync for the case where the
+ * caller can guarantee the timer does not reschedule itself in its timer
+ * function.
+ *
+ * Synchronization rules: callers must prevent restarting of the timer,
+ * otherwise this function is meaningless. It must not be called from
+ * interrupt contexts. Upon exit the timer is not queued and the handler
+ * is not running on any CPU.
+ *
+ * The function returns whether it has deactivated a pending timer or not.
+ */
+int del_singleshot_timer_sync(struct timer_list *timer)
+{
+ int ret = del_timer(timer);
+
+ if (!ret) {
+ ret = del_timer_sync(timer);
+ BUG_ON(ret);
+ }
+
+ return ret;
+}
+
+EXPORT_SYMBOL(del_singleshot_timer_sync);
#endif
static int cascade(tvec_base_t *base, tvec_t *tv, int index)
@@ -1109,7 +1138,7 @@
add_timer(&timer);
schedule();
- del_timer_sync(&timer);
+ del_singleshot_timer_sync(&timer);
timeout = expire - jiffies;
next reply other threads:[~2004-05-11 22:48 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-11 22:46 Geoff Gustafson [this message]
[not found] <40A152A8.4080104@linux.intel.com>
2004-05-11 23:03 ` [RFC] [PATCH] Performance of del_timer_sync Andrew Morton
-- strict thread matches above, loose matches on Subject: below --
2004-05-10 22:16 Geoff Gustafson
2004-05-11 7:45 ` Andrew Morton
2004-05-11 18:36 ` Geoff Gustafson
2004-05-11 19:11 ` Andrew Morton
2004-05-11 19:23 ` Chen, Kenneth W
2004-05-11 19:28 ` Andrew Morton
2004-05-11 19:30 ` Andrew Morton
2004-05-11 19:58 ` Ingo Molnar
2004-05-11 20:11 ` Andrew Morton
2004-05-11 20:19 ` Christoph Hellwig
2004-05-11 20:26 ` Andrew Morton
2004-05-11 20:32 ` Ingo Molnar
2004-05-11 20:55 ` Andrew Morton
2004-05-11 20:57 ` Ingo Molnar
2004-05-11 21:01 ` Chen, Kenneth W
2004-05-11 20:26 ` Ingo Molnar
2004-05-11 20:27 ` Chen, Kenneth W
2004-05-11 20:30 ` Andrew Morton
2004-05-11 20:45 ` Chen, Kenneth W
2004-05-11 20:38 ` Ingo Molnar
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=40A157CB.1010100@linux.intel.com \
--to=geoff@linux.jf.intel.com \
--cc=akpm@osdl.org \
--cc=hch@infradead.org \
--cc=kenneth.w.chen@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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