From: Stefano Brivio <sbrivio@redhat.com>
To: David Gibson <david@gibson.dropbear.id.au>
Cc: passt-dev@passt.top
Subject: Re: [PATCH 00/11] Simplify handling of "spliced" UDP forwarding
Date: Tue, 22 Nov 2022 22:51:43 +0100 [thread overview]
Message-ID: <20221122225143.4f3d630e@elisabeth> (raw)
In-Reply-To: <20221122034402.1517544-1-david@gibson.dropbear.id.au>
On Tue, 22 Nov 2022 14:43:51 +1100
David Gibson <david@gibson.dropbear.id.au> wrote:
> This series make some substantial simplifications to how we handle the
> forwarding of "spliced" UDP packets (those that don't go over the
> tuntap device, but instead are forwarded from one L4 socket to
> another).
>
> This doesn't yet change the existing (arguably broken) assumption that
> UDP communications are from one port to one port within the pasta
> namespace, not one to many or many to one. However, the
> simplifications made here will make it easier to correct that in
> future.
I'm not done reviewing this yet, but it all makes sense to me -- I just
need a bit longer to convince myself of 1/10 to 3/10 despite the fact
they're obviously simpler than the original implementation (i.e. of why
I didn't implement it like that in the first place ;)).
--
Stefano
prev parent reply other threads:[~2022-11-22 21:51 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-22 3:43 [PATCH 00/11] Simplify handling of "spliced" UDP forwarding David Gibson
2022-11-22 3:43 ` [PATCH 01/11] udp: Also bind() connected ports for "splice" forwarding David Gibson
2022-11-22 3:43 ` [PATCH 02/11] udp: Separate tracking of inbound and outbound packet flows David Gibson
2022-11-22 3:43 ` [PATCH 03/11] udp: Always use sendto() rather than send() for forwarding spliced packets David Gibson
2022-11-22 3:43 ` [PATCH 04/11] udp: Don't connect "forward" sockets for spliced flows David Gibson
2022-11-22 3:43 ` [PATCH 05/11] udp: Remove the @bound field from union udp_epoll_ref David Gibson
2022-11-22 3:43 ` [PATCH 06/11] udp: Split splice field in udp_epoll_ref into (mostly) independent bits David Gibson
2022-11-22 3:43 ` [PATCH 07/11] udp: Don't create double sockets for -U port David Gibson
2022-11-22 3:43 ` [PATCH 08/11] udp: Re-use fixed bound sockets for packet forwarding when possible David Gibson
2022-11-22 3:44 ` [PATCH 09/11] udp: Don't explicitly track originating socket for spliced "connections" David Gibson
2022-11-22 3:44 ` [PATCH 10/11] udp: Update UDP "connection" timestamps in both directions David Gibson
2022-11-22 3:44 ` [PATCH 11/11] udp: Simplify udp_sock_handler_splice David Gibson
2022-11-22 21:51 ` Stefano Brivio [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=20221122225143.4f3d630e@elisabeth \
--to=sbrivio@redhat.com \
--cc=david@gibson.dropbear.id.au \
--cc=passt-dev@passt.top \
/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.
Code repositories for project(s) associated with this public inbox
https://passt.top/passt
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for IMAP folder(s).