From: Peter Zijlstra <peterz@infradead.org>
To: Frederic Weisbecker <frederic@kernel.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
"Paul E . McKenney" <paulmck@linux.vnet.ibm.com>,
Ingo Molnar <mingo@kernel.org>,
stable@vger.kernel.org,
Anna-Maria Gleixner <anna-maria@linutronix.de>,
Jacek Tomaka <jacekt@dug.com>
Subject: Re: [PATCH] sched/nohz: Skip remote tick on idle task entirely
Date: Mon, 2 Jul 2018 14:44:43 +0200 [thread overview]
Message-ID: <20180702124443.GN2494@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <1530203381-31234-1-git-send-email-frederic@kernel.org>
On Thu, Jun 28, 2018 at 06:29:41PM +0200, Frederic Weisbecker wrote:
> ---
> kernel/sched/core.c | 18 ++++++++++--------
> 1 file changed, 10 insertions(+), 8 deletions(-)
>
> diff --git a/kernel/sched/core.c b/kernel/sched/core.c
> index 78d8fac..da8f121 100644
> --- a/kernel/sched/core.c
> +++ b/kernel/sched/core.c
> @@ -3127,16 +3127,18 @@ static void sched_tick_remote(struct work_struct *work)
> u64 delta;
>
> rq_lock_irq(rq, &rf);
> - update_rq_clock(rq);
> curr = rq->curr;
> - delta = rq_clock_task(rq) - curr->se.exec_start;
> + if (!is_idle_task(curr)) {
> + update_rq_clock(rq);
> + delta = rq_clock_task(rq) - curr->se.exec_start;
>
> - /*
> - * Make sure the next tick runs within a reasonable
> - * amount of time.
> - */
> - WARN_ON_ONCE(delta > (u64)NSEC_PER_SEC * 3);
> - curr->sched_class->task_tick(rq, curr, 0);
> + /*
> + * Make sure the next tick runs within a reasonable
> + * amount of time.
> + */
> + WARN_ON_ONCE(delta > (u64)NSEC_PER_SEC * 3);
> + curr->sched_class->task_tick(rq, curr, 0);
> + }
> rq_unlock_irq(rq, &rf);
> }
Instead of deep indent, how about we write it like so: ?
--- a/kernel/sched/core.c
+++ b/kernel/sched/core.c
@@ -3113,7 +3113,9 @@ static void sched_tick_remote(struct wor
struct tick_work *twork = container_of(dwork, struct tick_work, work);
int cpu = twork->cpu;
struct rq *rq = cpu_rq(cpu);
+ struct task_struct *curr;
struct rq_flags rf;
+ u64 delta;
/*
* Handle the tick only if it appears the remote CPU is running in full
@@ -3122,26 +3124,28 @@ static void sched_tick_remote(struct wor
* statistics and checks timeslices in a time-independent way, regardless
* of when exactly it is running.
*/
- if (!idle_cpu(cpu) && tick_nohz_tick_stopped_cpu(cpu)) {
- struct task_struct *curr;
- u64 delta;
-
- rq_lock_irq(rq, &rf);
- curr = rq->curr;
- if (!is_idle_task(curr)) {
- update_rq_clock(rq);
- delta = rq_clock_task(rq) - curr->se.exec_start;
-
- /*
- * Make sure the next tick runs within a reasonable
- * amount of time.
- */
- WARN_ON_ONCE(delta > (u64)NSEC_PER_SEC * 3);
- curr->sched_class->task_tick(rq, curr, 0);
- }
- rq_unlock_irq(rq, &rf);
- }
+ if (idle_cpu(cpu) || !tick_nohz_tick_stopped_cpu(cpu))
+ goto out_requeue;
+ rq_lock_irq(rq, &rf);
+ curr = rq->curr;
+ if (is_idle_task(curr))
+ goto out_unlock;
+
+ update_rq_clock(rq);
+ delta = rq_clock_task(rq) - curr->se.exec_start;
+
+ /*
+ * Make sure the next tick runs within a reasonable
+ * amount of time.
+ */
+ WARN_ON_ONCE(delta > (u64)NSEC_PER_SEC * 3);
+ curr->sched_class->task_tick(rq, curr, 0);
+
+out_unlock:
+ rq_unlock_irq(rq, &rf);
+
+out_requeue:
/*
* Run the remote tick once per second (1Hz). This arbitrary
* frequency is large enough to avoid overload but short enough
next prev parent reply other threads:[~2018-07-02 12:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-28 16:29 Frederic Weisbecker
2018-07-02 12:44 ` Peter Zijlstra [this message]
2018-07-02 15:17 ` Paul E. McKenney
2018-07-03 7:48 ` [tip:sched/core] " tip-bot for Frederic Weisbecker
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=20180702124443.GN2494@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=anna-maria@linutronix.de \
--cc=frederic@kernel.org \
--cc=jacekt@dug.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=paulmck@linux.vnet.ibm.com \
--cc=stable@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
all inboxes | Powered by JetHome®