From: Jens Axboe <axboe@kernel.dk>
To: Pavel Begunkov <asml.silence@gmail.com>,
io-uring@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/1] io_uring: optimise use of ctx->drain_next
Date: Thu, 16 Jan 2020 19:59:17 -0700 [thread overview]
Message-ID: <4b3d3147-260a-8649-c99b-681624762334@kernel.dk> (raw)
In-Reply-To: <6063bf6baa6fa1f5ec45272eb7c0b428698ded7f.1579222634.git.asml.silence@gmail.com>
On 1/16/20 5:57 PM, Pavel Begunkov wrote:
> Move setting ctx->drain_next to the only place it could be set, when it
> got linked non-head requests. The same for checking it, it's interesting
> only for a head of a link or a non-linked request.
>
> No functional changes here. This removes some code from the common path
> and also removes REQ_F_DRAIN_LINK flag, as it doesn't need it anymore.
Applied, thanks.
--
Jens Axboe
prev parent reply other threads:[~2020-01-17 2:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-17 0:57 [PATCH 1/1] io_uring: optimise use of ctx->drain_next Pavel Begunkov
2020-01-17 2:59 ` 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=4b3d3147-260a-8649-c99b-681624762334@kernel.dk \
--to=axboe@kernel.dk \
--cc=asml.silence@gmail.com \
--cc=io-uring@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).