From: Jens Axboe <axboe@kernel.dk>
To: "MOESSBAUER, Felix" <felix.moessbauer@siemens.com>,
"asml.silence@gmail.com" <asml.silence@gmail.com>
Cc: "io-uring@vger.kernel.org" <io-uring@vger.kernel.org>,
"cgroups@vger.kernel.org" <cgroups@vger.kernel.org>,
"Bezdeka, Florian" <florian.bezdeka@siemens.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"longman@redhat.com" <longman@redhat.com>,
"stable@vger.kernel.org" <stable@vger.kernel.org>,
"Schmidt, Adriaan" <adriaan.schmidt@siemens.com>,
"dqminh@cloudflare.com" <dqminh@cloudflare.com>
Subject: Re: [PATCH 1/1] io_uring/sqpoll: inherit cpumask of creating process
Date: Fri, 6 Sep 2024 07:55:07 -0600 [thread overview]
Message-ID: <10937dc5-ef82-4228-8724-c5a36f66985c@kernel.dk> (raw)
In-Reply-To: <236f0c6d019e8c25301f3db0a5c9d4971a094eb9.camel@siemens.com>
On 9/6/24 7:52 AM, MOESSBAUER, Felix wrote:
> On Fri, 2024-09-06 at 07:47 -0600, Jens Axboe wrote:
>> On 9/6/24 7:44 AM, Felix Moessbauer wrote:
>>> The submit queue polling threads are "kernel" threads that are
>>> started
>>
>> It's not a kernel thread, it's a normal userland thread that just
>> never
>> exits to userspace.
>
> One more reason to behave like a userland thread. I used the term
> "kernel" thread as it was used in commit a5fc1441af as well, referring
> to the same thing.
>
> Shall I update the commit message?
Not needed, I just amended it while committing.
--
Jens Axboe
next prev parent reply other threads:[~2024-09-06 13:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-06 13:44 [PATCH 1/1] io_uring/sqpoll: inherit cpumask of creating process Felix Moessbauer
2024-09-06 13:47 ` Jens Axboe
2024-09-06 13:52 ` MOESSBAUER, Felix
2024-09-06 13:55 ` Jens Axboe [this message]
2024-09-06 13:54 ` Jens Axboe
2024-09-06 16:00 ` Jens Axboe
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=10937dc5-ef82-4228-8724-c5a36f66985c@kernel.dk \
--to=axboe@kernel.dk \
--cc=adriaan.schmidt@siemens.com \
--cc=asml.silence@gmail.com \
--cc=cgroups@vger.kernel.org \
--cc=dqminh@cloudflare.com \
--cc=felix.moessbauer@siemens.com \
--cc=florian.bezdeka@siemens.com \
--cc=io-uring@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=longman@redhat.com \
--cc=stable@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox