From: "Zhang,Qiang" <qiang.zhang@windriver.com>
To: axboe@kernel.dk
Cc: viro@zeniv.linux.org.uk, io-uring@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Question on io-wq
Date: Thu, 22 Oct 2020 17:02:06 +0800 [thread overview]
Message-ID: <98c41fba-87fe-b08d-2c8c-da404f91ef31@windriver.com> (raw)
Hi Jens Axboe
There are some problem in 'io_wqe_worker' thread, when the
'io_wqe_worker' be create and Setting the affinity of CPUs in NUMA
nodes, due to CPU hotplug, When the last CPU going down, the
'io_wqe_worker' thread will run anywhere. when the CPU in the node goes
online again, we should restore their cpu bindings?
Thanks
Qiang
next reply other threads:[~2020-10-22 9:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-22 9:02 Zhang,Qiang [this message]
2020-10-22 14:08 ` Question on io-wq Jens Axboe
2020-10-23 3:55 ` 回复: " Zhang, Qiang
2020-10-23 3:57 ` Zhang, Qiang
[not found] ` <20201023020514.2230-1-hdanton@sina.com>
2020-10-23 2:24 ` Jens Axboe
2020-10-22 9:03 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=98c41fba-87fe-b08d-2c8c-da404f91ef31@windriver.com \
--to=qiang.zhang@windriver.com \
--cc=axboe@kernel.dk \
--cc=io-uring@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
/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;
as well as URLs for NNTP newsgroup(s).