From: Jens Axboe <axboe@kernel.dk>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Pavel Begunkov <asml.silence@gmail.com>,
io-uring <io-uring@vger.kernel.org>,
netdev <netdev@vger.kernel.org>
Subject: Re: [GIT PULL] io_uring support for zerocopy send
Date: Wed, 3 Aug 2022 10:47:36 -0600 [thread overview]
Message-ID: <ecca5fac-aa14-0023-e089-26e05ea68d46@kernel.dk> (raw)
In-Reply-To: <CAHk-=whxqSBtkvr4JijDBQ-yDrE91rFHt9D9b0jj=OMYL8mEsg@mail.gmail.com>
On 8/3/22 10:44 AM, Linus Torvalds wrote:
> On Wed, Aug 3, 2022 at 9:39 AM Jens Axboe <axboe@kernel.dk> wrote:
>>
>> If you look at the numbers Pavel posted, it's
>> definitely firmly in benchmark land, but I do think the goals of
>> breaking even with non zero-copy for realistic payload sizes is the real
>> differentiator here.
>
> Well, a big part of why I wrote the query email was exactly because I
> haven't seen any numbers, and the pull request didn't have any links
> to any.
>
> So you say "the numbers Pavel posted" and I say "where?"
Didn't think of that since it's in the git commit link, but I now
realize that it's like 3 series of things in there.
> It would have been good to have had a link in the pull request (and
> thus in the merge message).
Agree, it should've been in there. Here's the one from the series that
got merged:
https://lore.kernel.org/all/cover.1657643355.git.asml.silence@gmail.com/
--
Jens Axboe
next prev parent reply other threads:[~2022-08-03 16:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-31 15:03 [GIT PULL] io_uring support for zerocopy send Jens Axboe
2022-08-02 20:45 ` Linus Torvalds
2022-08-03 16:39 ` Jens Axboe
2022-08-03 16:44 ` Linus Torvalds
2022-08-03 16:47 ` Jens Axboe [this message]
2022-08-02 21:30 ` pr-tracker-bot
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=ecca5fac-aa14-0023-e089-26e05ea68d46@kernel.dk \
--to=axboe@kernel.dk \
--cc=asml.silence@gmail.com \
--cc=io-uring@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=torvalds@linux-foundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.