From: "Zhang, Qiang" <Qiang.Zhang@windriver.com>
To: Thomas Gleixner <tglx@linutronix.de>,
"pmladek@suse.com" <pmladek@suse.com>,
"tj@kernel.org" <tj@kernel.org>
Cc: "akpm@linux-foundation.org" <akpm@linux-foundation.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: 回复: [PATCH v2] kthread_worker: re-set CPU affinities if CPU come online
Date: Wed, 28 Oct 2020 08:45:36 +0000 [thread overview]
Message-ID: <BYAPR11MB263255ED056CED38285FC95BFF170@BYAPR11MB2632.namprd11.prod.outlook.com> (raw)
In-Reply-To: <874kme21nv.fsf@nanos.tec.linutronix.de>
________________________________________
发件人: Thomas Gleixner <tglx@linutronix.de>
发送时间: 2020年10月28日 16:30
收件人: Zhang, Qiang; pmladek@suse.com; tj@kernel.org
抄送: akpm@linux-foundation.org; linux-mm@kvack.org; linux-kernel@vger.kernel.org
主题: Re: [PATCH v2] kthread_worker: re-set CPU affinities if CPU come online
[Please note this e-mail is from an EXTERNAL e-mail address]
On Wed, Oct 28 2020 at 15:30, qiang zhang wrote:
> From: Zqiang <qiang.zhang@windriver.com>
>
> When someone CPU offlined, the 'kthread_worker' which bind this CPU,
> will run anywhere, if this CPU online, recovery of 'kthread_worker'
> affinity by cpuhp notifiers.
>
> Signed-off-by: Zqiang <qiang.zhang@windriver.com>
> ---
> v1->v2:
> rename variable kworker_online to kthread_worker_online.
> add 'cpuhp_node' and 'bind_cpu' init in KTHREAD_WORKER_INIT.
> add a comment explaining for WARN_ON_ONCE.
>How is that addressing any of the comments I made on V1 of this?
Do you mean the following problem:
"The dynamic hotplug states run late. What's preventing work to be queued
on such a worker before it is bound to the CPU again?"
Thanks
Qiang
>
>Thanks,
>
> tglx
next prev parent reply other threads:[~2020-10-28 8:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-28 7:30 qiang.zhang
2020-10-28 8:30 ` Thomas Gleixner
2020-10-28 8:45 ` Zhang, Qiang [this message]
2020-10-28 9:23 ` 回复: " Thomas Gleixner
2020-10-29 3:14 ` 回复: " Zhang, Qiang
2020-10-29 8:27 ` Thomas Gleixner
2020-10-29 13:08 ` Petr Mladek
2020-10-29 15:01 ` Thomas Gleixner
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=BYAPR11MB263255ED056CED38285FC95BFF170@BYAPR11MB2632.namprd11.prod.outlook.com \
--to=qiang.zhang@windriver.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=pmladek@suse.com \
--cc=tglx@linutronix.de \
--cc=tj@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox