From: Pavel Begunkov <[email protected]>
To: [email protected], [email protected]
Cc: Jens Axboe <[email protected]>,
"David S . Miller" <[email protected]>,
Jakub Kicinski <[email protected]>,
David Ahern <[email protected]>,
Eric Dumazet <[email protected]>,
Willem de Bruijn <[email protected]>,
Jason Wang <[email protected]>, Wei Liu <[email protected]>,
Paul Durrant <[email protected]>,
[email protected],
"Michael S . Tsirkin" <[email protected]>,
[email protected], [email protected]
Subject: Re: [PATCH io_uring-next/net-next v2 0/4] implement io_uring notification (ubuf_info) stacking
Date: Fri, 19 Apr 2024 12:21:30 +0100 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
On 4/19/24 12:08, Pavel Begunkov wrote:
> Please, don't take directly, conflicts with io_uring.
When everyone is happy with the patches, Jens and Jakub will hopefully
help to merge them. E.g. first staging net/ specific changes [1] and then
handling all conflicts on the io_uring side.
[1] https://github.com/isilence/linux.git iou-sendzc/notif-stacking-v2-netonly
> To have per request buffer notifications each zerocopy io_uring send
> request allocates a new ubuf_info. However, as an skb can carry only
> one uarg, it may force the stack to create many small skbs hurting
> performance in many ways.
>
> The patchset implements notification, i.e. an io_uring's ubuf_info
> extension, stacking. It attempts to link ubuf_info's into a list,
> allowing to have multiple of them per skb.
>
> liburing/examples/send-zerocopy shows up 6 times performance improvement
> for TCP with 4KB bytes per send, and levels it with MSG_ZEROCOPY. Without
> the patchset it requires much larger sends to utilise all potential.
>
> bytes | before | after (Kqps)
> 1200 | 195 | 1023
> 4000 | 193 | 1386
> 8000 | 154 | 1058
>
> The patches are on top of net-next + io_uring-next:
>
> https://github.com/isilence/linux.git iou-sendzc/notif-stacking-v2
>
> First two patches based on net-next:
>
> https://github.com/isilence/linux.git iou-sendzc/notif-stacking-v2-netonly
>
> v2: convert xen-netback to ubuf_info_ops (patch 1)
> drop two separately merged io_uring patches
>
> Pavel Begunkov (4):
> net: extend ubuf_info callback to ops structure
> net: add callback for setting a ubuf_info to skb
> io_uring/notif: simplify io_notif_flush()
> io_uring/notif: implement notification stacking
>
> drivers/net/tap.c | 2 +-
> drivers/net/tun.c | 2 +-
> drivers/net/xen-netback/common.h | 5 +-
> drivers/net/xen-netback/interface.c | 2 +-
> drivers/net/xen-netback/netback.c | 11 ++--
> drivers/vhost/net.c | 8 ++-
> include/linux/skbuff.h | 21 +++++---
> io_uring/notif.c | 83 +++++++++++++++++++++++++----
> io_uring/notif.h | 12 ++---
> net/core/skbuff.c | 36 ++++++++-----
> 10 files changed, 134 insertions(+), 48 deletions(-)
>
--
Pavel Begunkov
next prev parent reply other threads:[~2024-04-19 11:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-19 11:08 [PATCH io_uring-next/net-next v2 0/4] implement io_uring notification (ubuf_info) stacking Pavel Begunkov
2024-04-19 11:08 ` [PATCH io_uring-next/net-next v2 1/4] net: extend ubuf_info callback to ops structure Pavel Begunkov
2024-04-22 16:59 ` Willem de Bruijn
2024-04-19 11:08 ` [PATCH io_uring-next/net-next v2 2/4] net: add callback for setting a ubuf_info to skb Pavel Begunkov
2024-04-22 17:01 ` Willem de Bruijn
2024-04-19 11:08 ` [PATCH io_uring-next/net-next v2 3/4] io_uring/notif: simplify io_notif_flush() Pavel Begunkov
2024-04-19 11:08 ` [PATCH io_uring-next/net-next v2 4/4] io_uring/notif: implement notification stacking Pavel Begunkov
2024-04-19 11:21 ` Pavel Begunkov [this message]
2024-04-23 0:20 ` [PATCH io_uring-next/net-next v2 0/4] implement io_uring notification (ubuf_info) stacking patchwork-bot+netdevbpf
2024-04-23 1:36 ` (subset) " Jens Axboe
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] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[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