From: Jens Axboe <[email protected]>
To: Hao Xu <[email protected]>, [email protected]
Cc: Pavel Begunkov <[email protected]>
Subject: Re: [PATCH] io_uring: kbuf: inline io_kbuf_recycle_ring()
Date: Thu, 23 Jun 2022 06:22:29 -0600 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
On 6/23/22 1:17 AM, Hao Xu wrote:
> From: Hao Xu <[email protected]>
>
> Make io_kbuf_recycle_ring() inline since it is the fast path of
> provided buffer.
The legacy recycling path doesn't need to get inlined, it's
too fat for that. Let's just move io_kbuf_recycle_ring() and leave
io_kbuf_recycle_legacy() out-of-line in kbuf.c as a function call.
--
Jens Axboe
prev parent reply other threads:[~2022-06-23 12:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-23 7:17 [PATCH] io_uring: kbuf: inline io_kbuf_recycle_ring() Hao Xu
2022-06-23 12: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 \
[email protected] \
[email protected] \
[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