All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: Lai Jiangshan <jiangshanlai@gmail.com>
Cc: Valentin Schneider <valentin.schneider@arm.com>,
	Ingo Molnar <mingo@kernel.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	LKML <linux-kernel@vger.kernel.org>, Qian Cai <cai@redhat.com>,
	Vincent Donnefort <vincent.donnefort@arm.com>,
	Dexuan Cui <decui@microsoft.com>,
	"Paul E. McKenney" <paulmck@kernel.org>,
	Vincent Guittot <vincent.guittot@linaro.org>,
	Steven Rostedt <rostedt@goodmis.org>, Tejun Heo <tj@kernel.org>
Subject: Re: [PATCH 3/4] workqueue: Tag bound workers with KTHREAD_IS_PER_CPU
Date: Sat, 16 Jan 2021 13:45:23 +0100	[thread overview]
Message-ID: <YALf4xDwTKCERPbf@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <CAJhGHyBazDix9tLTV0HnobeSzneUK8Y9GKf6AgXspf=c9O5dhQ@mail.gmail.com>

On Sat, Jan 16, 2021 at 02:27:09PM +0800, Lai Jiangshan wrote:
> On Thu, Jan 14, 2021 at 11:35 PM Peter Zijlstra <peterz@infradead.org> wrote:
> 
> >
> > -void kthread_set_per_cpu(struct task_struct *k, bool set)
> > +void kthread_set_per_cpu(struct task_struct *k, int cpu)
> >  {
> >         struct kthread *kthread = to_kthread(k);
> >         if (!kthread)
> >                 return;
> >
> > -       if (set) {
> > -               WARN_ON_ONCE(!(k->flags & PF_NO_SETAFFINITY));
> > -               WARN_ON_ONCE(k->nr_cpus_allowed != 1);
> > -               set_bit(KTHREAD_IS_PER_CPU, &kthread->flags);
> > -       } else {
> > +       WARN_ON_ONCE(!(k->flags & PF_NO_SETAFFINITY));
> > +
> > +       if (cpu < 0) {
> >                 clear_bit(KTHREAD_IS_PER_CPU, &kthread->flags);
> > +               return;
> >         }
> > +
> > +       kthread->cpu = cpu;
> > +       set_bit(KTHREAD_IS_PER_CPU, &kthread->flags);
> >  }
> >
> 
> I don't see the code to set the mask of the cpu to the task
> since set_cpus_allowed_ptr() is removed from rebind_worker().
> 
> Is it somewhere I missed?

kthread_unpark().

> > @@ -4978,9 +4982,9 @@ static void rebind_workers(struct worker_pool *pool)
> >          * from CPU_ONLINE, the following shouldn't fail.
> >          */
> >         for_each_pool_worker(worker, pool) {
> > -               WARN_ON_ONCE(set_cpus_allowed_ptr(worker->task,
> > -                                                 pool->attrs->cpumask) < 0);
> > -               kthread_set_per_cpu(worker->task, true);
> > +               WARN_ON_ONCE(kthread_park(worker->task) < 0);
> > +               kthread_set_per_cpu(worker->task, pool->cpu);
> > +               kthread_unpark(worker->task);
> 
> I feel nervous to use kthread_park() here and kthread_parkme() in
> worker thread.  And adding kthread_should_park() to the fast path
> also daunt me.

Is that really such a hot path that an additional load is problematic?

> How about using a new KTHREAD_XXXX instead of KTHREAD_IS_PER_CPU,
> so that we can set and clear KTHREAD_XXXX freely, especially before
> set_cpus_allowed_ptr().

KTHREAD_IS_PER_CPU is exactly what we need, why make another flag?

The above sequence is nice in that it restores both the
KTHREAD_IS_PER_CPU flag and affinity while the task is frozen, so there
are no races where one is observed and not the other.

It is also the exact sequence normal per-cpu threads (smpboot) use to
preserve affinity.

  reply	other threads:[~2021-01-16 12:47 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-12 14:43 [PATCH 0/4] sched: Fix hot-unplug regressions Peter Zijlstra
2021-01-12 14:43 ` [PATCH 2/4] kthread: Extract KTHREAD_IS_PER_CPU Peter Zijlstra
2021-01-12 14:43 ` [PATCH 3/4] workqueue: Tag bound workers with KTHREAD_IS_PER_CPU Peter Zijlstra
2021-01-12 16:36   ` Lai Jiangshan
2021-01-13 11:43     ` Peter Zijlstra
2021-01-12 17:57   ` Valentin Schneider
2021-01-13 13:28   ` Lai Jiangshan
2021-01-13 14:16     ` Valentin Schneider
2021-01-13 17:52       ` Paul E. McKenney
2021-01-13 18:43         ` Valentin Schneider
2021-01-13 18:59           ` Paul E. McKenney
2021-01-14 13:12     ` Peter Zijlstra
2021-01-14 13:21       ` Valentin Schneider
2021-01-14 15:34         ` Peter Zijlstra
2021-01-16  6:27           ` Lai Jiangshan
2021-01-16 12:45             ` Peter Zijlstra [this message]
2021-01-16 14:45               ` Lai Jiangshan
2021-01-16 15:16                 ` Peter Zijlstra
2021-01-16 16:14                   ` Lai Jiangshan
2021-01-16 18:46                     ` Peter Zijlstra
2021-01-17  9:54                       ` Peter Zijlstra
2021-01-16 15:13               ` Peter Zijlstra
2021-01-12 14:43 ` [PATCH 4/4] sched: Fix CPU hotplug / tighten is_per_cpu_kthread() Peter Zijlstra

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=YALf4xDwTKCERPbf@hirez.programming.kicks-ass.net \
    --to=peterz@infradead.org \
    --cc=cai@redhat.com \
    --cc=decui@microsoft.com \
    --cc=jiangshanlai@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=paulmck@kernel.org \
    --cc=rostedt@goodmis.org \
    --cc=tglx@linutronix.de \
    --cc=tj@kernel.org \
    --cc=valentin.schneider@arm.com \
    --cc=vincent.donnefort@arm.com \
    --cc=vincent.guittot@linaro.org \
    /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.