From: Jens Axboe <axboe@kernel.dk>
To: Christophe JAILLET <christophe.jaillet@wanadoo.fr>,
Breno Leitao <leitao@debian.org>,
Pavel Begunkov <asml.silence@gmail.com>
Cc: leit@meta.com, "open list:IO_URING" <io-uring@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] io_uring/io-wq: Use set_bit() and test_bit() at worker->flags
Date: Fri, 3 May 2024 13:36:38 -0600 [thread overview]
Message-ID: <0f9c6f92-7160-46b1-86ee-2a4233c7860f@kernel.dk> (raw)
In-Reply-To: <75ae8634-72ad-4c6f-92af-76eaa1d3b1d9@wanadoo.fr>
On 5/3/24 1:24 PM, Christophe JAILLET wrote:
> Le 03/05/2024 ? 20:41, Jens Axboe a ?crit :
>> On 5/3/24 11:37 AM, Breno Leitao wrote:
>>> @@ -631,7 +631,8 @@ static int io_wq_worker(void *data)
>>> bool exit_mask = false, last_timeout = false;
>>> char buf[TASK_COMM_LEN];
>>> - worker->flags |= (IO_WORKER_F_UP | IO_WORKER_F_RUNNING);
>>> + set_bit(IO_WORKER_F_UP, &worker->flags);
>>> + set_bit(IO_WORKER_F_RUNNING, &worker->flags);
>>
>> You could probably just use WRITE_ONCE() here with the mask, as it's
>> setup side.
>>
>
> Or simply:
> set_mask_bits(&worker->flags, 0, IO_WORKER_F_UP | IO_WORKER_F_RUNNING);
Looks like overkill, as we don't really need that kind of assurances
here. WRITE_ONCE should be fine. Not that it _really_ matters as it's
not a performance critical part, but it also sends wrong hints to the
reader of the code on which kind of guarantees are needing here.
--
Jens Axboe
next prev parent reply other threads:[~2024-05-03 19:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-03 17:37 Breno Leitao
2024-05-03 18:32 ` Jens Axboe
2024-05-07 10:44 ` Breno Leitao
2024-05-07 11:02 ` Breno Leitao
2024-05-07 13:28 ` Jens Axboe
2024-05-03 18:41 ` Jens Axboe
2024-05-03 19:24 ` Christophe JAILLET
2024-05-03 19:36 ` Jens Axboe [this message]
2024-05-07 9:24 ` Breno Leitao
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=0f9c6f92-7160-46b1-86ee-2a4233c7860f@kernel.dk \
--to=axboe@kernel.dk \
--cc=asml.silence@gmail.com \
--cc=christophe.jaillet@wanadoo.fr \
--cc=io-uring@vger.kernel.org \
--cc=leit@meta.com \
--cc=leitao@debian.org \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®