From: Jens Axboe <[email protected]>
To: [email protected], Pavel Begunkov <[email protected]>
Subject: Re: [PATCH for-next 0/2] inline execution ltimeout optimisation
Date: Sun, 03 Dec 2023 08:22:17 -0700 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
On Fri, 01 Dec 2023 00:38:51 +0000, Pavel Begunkov wrote:
> Patches are not related but put touch adjacent lines. First we improve
> a little bit on post issue iopoll checks, and then return back a long
> lost linked timeout optimisation.
>
> Pavel Begunkov (2):
> io_uring: don't check iopoll if request completes
> io_uring: optimise ltimeout for inline execution
>
> [...]
Applied, thanks!
[1/2] io_uring: don't check iopoll if request completes
(no commit info)
[2/2] io_uring: optimise ltimeout for inline execution
(no commit info)
Best regards,
--
Jens Axboe
prev parent reply other threads:[~2023-12-03 15:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-01 0:38 [PATCH for-next 0/2] inline execution ltimeout optimisation Pavel Begunkov
2023-12-01 0:38 ` [PATCH for-next 1/2] io_uring: don't check iopoll if request completes Pavel Begunkov
2023-12-01 0:38 ` [PATCH for-next 2/2] io_uring: optimise ltimeout for inline execution Pavel Begunkov
2023-12-01 19:03 ` Pavel Begunkov
2023-12-03 15:22 ` 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=170161693776.938596.9769381596057904599.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