public inbox for [email protected]
 help / color / mirror / Atom feed
From: Jens Axboe <[email protected]>
To: [email protected], Pavel Begunkov <[email protected]>
Subject: Re: [RFC 1/1] io_uring: pin context while queueing deferred tw
Date: Wed, 04 Jan 2023 09:13:51 -0700	[thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <1a79362b9c10b8523ef70b061d96523650a23344.1672795998.git.asml.silence@gmail.com>


On Wed, 04 Jan 2023 01:34:02 +0000, Pavel Begunkov wrote:
> Unlike normal tw, nothing prevents deferred tw to be executed right
> after an tw item added to ->work_llist in io_req_local_work_add(). For
> instance, the waiting task may get waken up by CQ posting or a normal
> tw. Thus we need to pin the ring for the rest of io_req_local_work_add()
> 
> 

Applied, thanks!

[1/1] io_uring: pin context while queueing deferred tw
      (no commit info)

Best regards,
-- 
Jens Axboe



             reply	other threads:[~2023-01-04 16:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-04 16:13 Jens Axboe [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-01-04  1:34 [RFC 1/1] io_uring: pin context while queueing deferred tw Pavel Begunkov
2023-01-04  1:36 ` Pavel Begunkov

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=167284883119.63338.188865590110226329.b4-ty@kernel.dk \
    [email protected] \
    [email protected] \
    [email protected] \
    /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