From: "Michal Koutný" <email@example.com>
To: Jens Axboe <firstname.lastname@example.org>, Hao Xu <email@example.com>
Cc: Zefan Li <firstname.lastname@example.org>, Tejun Heo <email@example.com>,
Johannes Weiner <firstname.lastname@example.org>,
Pavel Begunkov <email@example.com>,
Joseph Qi <firstname.lastname@example.org>
Subject: Re: [PATCH v4 0/2] refactor sqthread cpu binding logic
Date: Thu, 9 Sep 2021 14:34:05 +0200 [thread overview]
Message-ID: <20210909123405.GA7872@blackbody.suse.cz> (raw)
Thanks for the answer and the context explanations.
On Thu, Sep 02, 2021 at 12:00:33PM -0600, Jens Axboe <email@example.com> wrote:
> We already have this API to set the affinity based on when these were
> regular kernel threads, so it needs to work with that too. As such they
> are marked PF_NO_SETAFFINITY.
I see the current implementation "allows" at most one binding (by the
passed sq_cpu arg) to a CPU and then "locks" it by setting
PF_NO_SETAFFINITY subsequently (after set_cpus_allowed_ptr).
And actually doesn't check whether it succeeded or not (Hao suggests in
another subthread sq_cpu is a mere hint).
Nevertheless, you likely don't want to "trespass" the boundary of a
cpuset and I think that it'll end up with a loop checking against
hotplug races. That is already implemented in __sched_affinity, it'd be
IMO good to have it in one place only.
> >  Not only spending their life in kernel but providing some
> > delocalized kernel service.
> That's what they do...
(I assume that answer to "life in kernel" and the IO threads serve only
the originating cpuset (container) i.e. are (co)localized to it (not
delocalized as some kernel workers).)
next prev parent reply other threads:[~2021-09-09 12:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-01 12:43 [PATCH v4 0/2] refactor sqthread cpu binding logic Hao Xu
2021-09-01 12:43 ` [PATCH 1/2] cpuset: add a helper to check if cpu in cpuset of current task Hao Xu
2021-09-01 12:43 ` [PATCH 2/2] io_uring: consider cgroup setting when binding sqpoll cpu Hao Xu
2021-09-01 16:41 ` Tejun Heo
2021-09-01 16:42 ` Tejun Heo
2021-09-03 15:04 ` Hao Xu
2021-09-07 16:54 ` Tejun Heo
2021-09-07 19:28 ` Hao Xu
2021-09-02 16:48 ` [PATCH v4 0/2] refactor sqthread cpu binding logic Michal Koutný
2021-09-02 18:00 ` Jens Axboe
2021-09-09 12:34 ` Michal Koutný [this message]
2021-09-03 14:43 ` Hao Xu
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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.