public inbox for io-uring@vger.kernel.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: io-uring@vger.kernel.org, Pavel Begunkov <asml.silence@gmail.com>
Subject: Re: [PATCH 1/1] io_uring: always do atomic put from iowq
Date: Thu, 03 Apr 2025 08:32:20 -0600	[thread overview]
Message-ID: <174369074004.172837.7459354560566437088.b4-ty@kernel.dk> (raw)
In-Reply-To: <d880bc27fb8c3209b54641be4ff6ac02b0e5789a.1743679736.git.asml.silence@gmail.com>


On Thu, 03 Apr 2025 12:29:30 +0100, Pavel Begunkov wrote:
> io_uring always switches requests to atomic refcounting for iowq
> execution before there is any parallilism by setting REQ_F_REFCOUNT,
> and the flag is not cleared until the request completes. That should be
> fine as long as the compiler doesn't make up a non existing value for
> the flags, however KCSAN still complains when the request owner changes
> oter flag bits:
> 
> [...]

Applied, thanks!

[1/1] io_uring: always do atomic put from iowq
      commit: 390513642ee6763c7ada07f0a1470474986e6c1c

Best regards,
-- 
Jens Axboe




      reply	other threads:[~2025-04-03 14:32 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-03 11:29 [PATCH 1/1] io_uring: always do atomic put from iowq Pavel Begunkov
2025-04-03 14:32 ` Jens Axboe [this message]

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=174369074004.172837.7459354560566437088.b4-ty@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=asml.silence@gmail.com \
    --cc=io-uring@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