All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: "Zhang, Qiang" <Qiang.Zhang@windriver.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: Question on   workqueue: Manually break affinity on hotplug
Date: Thu, 14 Jan 2021 10:11:48 +0100	[thread overview]
Message-ID: <YAAK1MOPAPjrbSIt@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <BYAPR11MB2632FC41FF64133708F4537FFFA80@BYAPR11MB2632.namprd11.prod.outlook.com>

On Thu, Jan 14, 2021 at 08:03:23AM +0000, Zhang, Qiang wrote:
> Hello Peter
> 
> Excuse me, I have some questions for you, about a description of this change:
> 
> ''Don't rely on the scheduler to force break affinity for us -- it will
> stop doing that for per-cpu-kthreads."
> 
> this mean when cpuhotplug, scheduler do not  change  affinity for per-cpu-kthread's task, if we not active setting affinity?
> but if per-cpu-kthread's task is not run state, when wake up,  will reset it's affinity, this  is done automatically.
> 
> or is it,  this place modified to fit the new one hotplug mechanism which
> ("sched/hotplug: Consolidate task migration on CPU unplug")?

https://lkml.kernel.org/r/20201214155457.3430-1-jiangshanlai@gmail.com
https://lkml.kernel.org/r/20201218170919.2950-1-jiangshanlai@gmail.com
https://lkml.kernel.org/r/20201226025117.2770-1-jiangshanlai@gmail.com
https://lkml.kernel.org/r/20210111152638.2417-1-jiangshanlai@gmail.com
https://lkml.kernel.org/r/20210112144344.850850975@infradead.org

  reply	other threads:[~2021-01-14  9:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-14  8:03 Question on workqueue: Manually break affinity on hotplug Zhang, Qiang
2021-01-14  9:11 ` Peter Zijlstra [this message]
2021-01-17 10:16   ` 回复: " Zhang, Qiang

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=YAAK1MOPAPjrbSIt@hirez.programming.kicks-ass.net \
    --to=peterz@infradead.org \
    --cc=Qiang.Zhang@windriver.com \
    --cc=linux-kernel@vger.kernel.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.