From: "蒋雄伟(蒋冲)" <xiongwei.jiang@alibaba-inc.com>
To: <linux-kernel@vger.kernel.org>
Cc: <shli@kernel.org>, <neilb@suse.de>
Subject: raid5: how to bind worker threads to specified cpus
Date: Thu, 13 Sep 2018 16:18:48 +0800 [thread overview]
Message-ID: <003401d44b3a$65afbf70$310f3e50$@alibaba-inc.com> (raw)
Since commit b721420e8719131896b009b11edbbd27d9b85e98, raid5 has been
enabled to support workqueue offload handling of stripes. However, if I hope
to bind worker threads to specified cpus, for example 0-3, is it possible?
The reason for doing this is that I hope applications will not be disturbed
by raid5's jobs. My naive idea is to add a field named "affinity_hint" to
struct r5conf, and then add a sysfs entry to input cpu list, and then take
stripe_head's sector as the hash key to evenly distribute stripe_head across
the cpus.
Anyone has suggestion about my idea or any alternative solutions to bind
worker threads to specified cpus ? thanks a lot .
reply other threads:[~2018-09-13 8:19 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='003401d44b3a$65afbf70$310f3e50$@alibaba-inc.com' \
--to=xiongwei.jiang@alibaba-inc.com \
--cc=linux-kernel@vger.kernel.org \
--cc=neilb@suse.de \
--cc=shli@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
all inboxes | Powered by JetHome®