public inbox for [email protected]
 help / color / mirror / Atom feed
From: Victor Stewart <[email protected]>
To: [email protected]
Subject: allowing msg_name and msg_control
Date: Sat, 7 Nov 2020 14:22:54 +0000	[thread overview]
Message-ID: <CAM1kxwhuVfkofDXKaeW4J6Khy2Jp3UcXALQ4SdP9Okk_w7zjNg@mail.gmail.com> (raw)

RE Jen's proposed patch here
https://lore.kernel.org/io-uring/[email protected]/

and RE what Stefan just mentioned in the "[PATCH 5.11] io_uring: don't
take fs for recvmsg/sendmsg" thread a few minutes ago... "Can't we
better remove these checks and allow msg_control? For me it's a
limitation that I would like to be removed."... which I coincidentally
just read when coming on here to advocate the same.

I also require this for a few vital performance use cases:

1) GSO (UDP_SEGMENT to sendmsg)
2) GRO (UDP_GRO from recvmsg)

GSO and GRO are super important for QUIC servers... essentially
bringing a 3-4x performance improvement that brings them in line with
TCP efficiency.

Would also allow the usage of...

3) MSG_ZEROCOPY (to receive the sock_extended_err from recvmsg)

it's only a single digit % performance gain for large sends (but a
minor crutch until we get registered buffer sendmsg / recvmsg, which I
plan on implementing).

So if there's an agreed upon plan on action I can take charge of all
the work and get this done ASAP.

#Victor

             reply	other threads:[~2020-11-07 14:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-07 14:22 Victor Stewart [this message]
2020-11-07 16:21 ` allowing msg_name and msg_control Pavel Begunkov
2020-11-07 17:12   ` Victor Stewart
2020-11-07 20:15     ` Pavel Begunkov

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=CAM1kxwhuVfkofDXKaeW4J6Khy2Jp3UcXALQ4SdP9Okk_w7zjNg@mail.gmail.com \
    [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