From: Soheil Hassas Yeganeh <[email protected]>
To: Victor Stewart <[email protected]>
Cc: io-uring <[email protected]>,
netdev <[email protected]>, Jann Horn <[email protected]>
Subject: Re: [PATCH v3] Allow UDP cmsghdrs through io_uring
Date: Sun, 13 Dec 2020 21:22:22 -0500 [thread overview]
Message-ID: <CACSApvbAXTN9VLcB0BphbJffZ8YXpxm=JF8FteKBVkBArwcd3A@mail.gmail.com> (raw)
In-Reply-To: <[email protected]>
On Sun, Dec 13, 2020 at 3:43 PM Victor Stewart <[email protected]> wrote:
>
> here we go, figured it out. sorry about that.
>
> This patch adds PROTO_CMSG_DATA_ONLY to inet_dgram_ops and inet6_dgram_ops so that UDP_SEGMENT (GSO) and UDP_GRO can be used through io_uring.
The v3 patch doesn't have "Signed-off-by". You can see all the checks
on patchwork:
https://patchwork.kernel.org/project/netdevbpf/patch/[email protected]/
For patches to netdev, please include the target. Here it should be net-next:
https://www.kernel.org/doc/Documentation/networking/netdev-FAQ.txt
git format-patch --subject-prefix='PATCH net-next v4' ...
Also, since this patch affects udp, it's preferred to include "udp: "
in your commit's subject line. In other words, the v4 of this patch
should look like the following:
[PATCH net-next v2] udp: allow UDP cmsghdrs through io_uring
Thank you
> GSO and GRO are vital to bring QUIC servers on par with TCP throughputs, and together offer a higher
> throughput gain than io_uring alone (rate of data transit
> considering), thus io_uring is presently the lesser performance choice.
>
> RE http://vger.kernel.org/lpc_net2018_talks/willemdebruijn-lpc2018-udpgso-paper-DRAFT-1.pdf,
> GSO is about +~63% and GRO +~82%.
>
> this patch closes that loophole.
>
> net/ipv4/af_inet.c | 1 +
> net/ipv6/af_inet6.c | 1 +
> net/socket.c | 8 +++++---
> 3 files changed, 7 insertions(+), 3 deletions(-)
>
>
prev parent reply other threads:[~2020-12-14 2:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-13 20:43 [PATCH v3] Allow UDP cmsghdrs through io_uring Victor Stewart
2020-12-13 20:43 ` Victor Stewart
2020-12-14 2:22 ` Soheil Hassas Yeganeh [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='CACSApvbAXTN9VLcB0BphbJffZ8YXpxm=JF8FteKBVkBArwcd3A@mail.gmail.com' \
[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