Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1234346 > unrolled thread
| Started by | Yunhong Jiang <yunhong.jiang@linux.intel.com> |
|---|---|
| First post | 2015-09-28 21:00 +0200 |
| Last post | 2015-10-11 20:20 +0200 |
| Articles | 3 — 2 participants |
Back to article view | Back to linux.kernel
[PATCH] timer: Lazily wakup nohz CPU when adding new timer. Yunhong Jiang <yunhong.jiang@linux.intel.com> - 2015-09-28 21:00 +0200
Re: [PATCH] timer: Lazily wakup nohz CPU when adding new timer. Yunhong Jiang <yunhong.jiang@linux.intel.com> - 2015-10-05 23:10 +0200
Re: [PATCH] timer: Lazily wakup nohz CPU when adding new timer. Thomas Gleixner <tglx@linutronix.de> - 2015-10-11 20:20 +0200
| From | Yunhong Jiang <yunhong.jiang@linux.intel.com> |
|---|---|
| Date | 2015-09-28 21:00 +0200 |
| Subject | [PATCH] timer: Lazily wakup nohz CPU when adding new timer. |
| Message-ID | <qdLOy-7Vg-11@gated-at.bofh.it> |
Currently, when a new timer added to timer wheel for a nohz_active CPU,
the target CPU will always be waked up.
In fact, if the new added timer is after the base->next_timer, we don't
need wake up the target CPU since it will not change the sleep time. A
lazy wake up is better in such scenario.
I cooked a test scenario. On my 32 cores system, a driver on CPU 15
continuous enqueues timer to CPU 8/9/10/11 with random expire and then
checks the idle_calls difference after 10 seconds. Below data shows
that lazy wake up do reduce the wakeup a lot.
w/o Lazy w/ lazy
CPU 8: 135 88
CPU 9: 238 43
CPU 10: 157 83
CPU 11: 172 70
Signed-off-by: Yunhong Jiang <yunhong.jiang@linux.intel.com>
---
kernel/time/timer.c | 21 ++++++++++++++-------
1 file changed, 14 insertions(+), 7 deletions(-)
diff --git a/kernel/time/timer.c b/kernel/time/timer.c
index d3f5e92f722a..a039d9e6b55a 100644
--- a/kernel/time/timer.c
+++ b/kernel/time/timer.c
@@ -414,6 +414,8 @@ __internal_add_timer(struct tvec_base *base, struct timer_list *timer)
static void internal_add_timer(struct tvec_base *base, struct timer_list *timer)
{
+ bool kick_nohz = false;
+
/* Advance base->jiffies, if the base is empty */
if (!base->all_timers++)
base->timer_jiffies = jiffies;
@@ -424,9 +426,17 @@ static void internal_add_timer(struct tvec_base *base, struct timer_list *timer)
*/
if (!(timer->flags & TIMER_DEFERRABLE)) {
if (!base->active_timers++ ||
- time_before(timer->expires, base->next_timer))
+ time_before(timer->expires, base->next_timer)) {
base->next_timer = timer->expires;
- }
+ /*
+ * CPU in dynticks need reevaluate the timer wheel
+ * if newer timer added with next_timer updated.
+ */
+ if (base->nohz_active)
+ kick_nohz = true;
+ }
+ } else if (base->nohz_active && tick_nohz_full_cpu(base->cpu))
+ kick_nohz = true;
/*
* Check whether the other CPU is in dynticks mode and needs
@@ -441,11 +451,8 @@ static void internal_add_timer(struct tvec_base *base, struct timer_list *timer)
* require special care against races with idle_cpu(), lets deal
* with that later.
*/
- if (base->nohz_active) {
- if (!(timer->flags & TIMER_DEFERRABLE) ||
- tick_nohz_full_cpu(base->cpu))
- wake_up_nohz_cpu(base->cpu);
- }
+ if (kick_nohz)
+ wake_up_nohz_cpu(base->cpu);
}
#ifdef CONFIG_TIMER_STATS
--
1.8.3.1
--
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/
[toc] | [next] | [standalone]
| From | Yunhong Jiang <yunhong.jiang@linux.intel.com> |
|---|---|
| Date | 2015-10-05 23:10 +0200 |
| Message-ID | <qglbc-2cb-35@gated-at.bofh.it> |
| In reply to | #1234346 |
Ping for any response.
Thanks
--jyh
On Mon, Sep 28, 2015 at 11:48:16AM -0700, Yunhong Jiang wrote:
> Currently, when a new timer added to timer wheel for a nohz_active CPU,
> the target CPU will always be waked up.
>
> In fact, if the new added timer is after the base->next_timer, we don't
> need wake up the target CPU since it will not change the sleep time. A
> lazy wake up is better in such scenario.
>
> I cooked a test scenario. On my 32 cores system, a driver on CPU 15
> continuous enqueues timer to CPU 8/9/10/11 with random expire and then
> checks the idle_calls difference after 10 seconds. Below data shows
> that lazy wake up do reduce the wakeup a lot.
>
> w/o Lazy w/ lazy
> CPU 8: 135 88
> CPU 9: 238 43
> CPU 10: 157 83
> CPU 11: 172 70
>
> Signed-off-by: Yunhong Jiang <yunhong.jiang@linux.intel.com>
> ---
> kernel/time/timer.c | 21 ++++++++++++++-------
> 1 file changed, 14 insertions(+), 7 deletions(-)
>
> diff --git a/kernel/time/timer.c b/kernel/time/timer.c
> index d3f5e92f722a..a039d9e6b55a 100644
> --- a/kernel/time/timer.c
> +++ b/kernel/time/timer.c
> @@ -414,6 +414,8 @@ __internal_add_timer(struct tvec_base *base, struct timer_list *timer)
>
> static void internal_add_timer(struct tvec_base *base, struct timer_list *timer)
> {
> + bool kick_nohz = false;
> +
> /* Advance base->jiffies, if the base is empty */
> if (!base->all_timers++)
> base->timer_jiffies = jiffies;
> @@ -424,9 +426,17 @@ static void internal_add_timer(struct tvec_base *base, struct timer_list *timer)
> */
> if (!(timer->flags & TIMER_DEFERRABLE)) {
> if (!base->active_timers++ ||
> - time_before(timer->expires, base->next_timer))
> + time_before(timer->expires, base->next_timer)) {
> base->next_timer = timer->expires;
> - }
> + /*
> + * CPU in dynticks need reevaluate the timer wheel
> + * if newer timer added with next_timer updated.
> + */
> + if (base->nohz_active)
> + kick_nohz = true;
> + }
> + } else if (base->nohz_active && tick_nohz_full_cpu(base->cpu))
> + kick_nohz = true;
>
> /*
> * Check whether the other CPU is in dynticks mode and needs
> @@ -441,11 +451,8 @@ static void internal_add_timer(struct tvec_base *base, struct timer_list *timer)
> * require special care against races with idle_cpu(), lets deal
> * with that later.
> */
> - if (base->nohz_active) {
> - if (!(timer->flags & TIMER_DEFERRABLE) ||
> - tick_nohz_full_cpu(base->cpu))
> - wake_up_nohz_cpu(base->cpu);
> - }
> + if (kick_nohz)
> + wake_up_nohz_cpu(base->cpu);
> }
>
> #ifdef CONFIG_TIMER_STATS
> --
> 1.8.3.1
>
> --
> 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/
--
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/
[toc] | [prev] | [next] | [standalone]
| From | Thomas Gleixner <tglx@linutronix.de> |
|---|---|
| Date | 2015-10-11 20:20 +0200 |
| Message-ID | <qitnY-7Pn-11@gated-at.bofh.it> |
| In reply to | #1234346 |
On Mon, 28 Sep 2015, Yunhong Jiang wrote:
> static void internal_add_timer(struct tvec_base *base, struct timer_list *timer)
> {
> + bool kick_nohz = false;
> +
> /* Advance base->jiffies, if the base is empty */
> if (!base->all_timers++)
> base->timer_jiffies = jiffies;
> @@ -424,9 +426,17 @@ static void internal_add_timer(struct tvec_base *base, struct timer_list *timer)
> */
> if (!(timer->flags & TIMER_DEFERRABLE)) {
> if (!base->active_timers++ ||
> - time_before(timer->expires, base->next_timer))
> + time_before(timer->expires, base->next_timer)) {
> base->next_timer = timer->expires;
> - }
> + /*
> + * CPU in dynticks need reevaluate the timer wheel
> + * if newer timer added with next_timer updated.
> + */
> + if (base->nohz_active)
> + kick_nohz = true;
> + }
> + } else if (base->nohz_active && tick_nohz_full_cpu(base->cpu))
> + kick_nohz = true;
Why do you want to kick the other cpu when a deferrable timer got added?
Thanks,
tglx
--
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/
[toc] | [prev] | [standalone]
Back to top | Article view | linux.kernel
csiph-web