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.
Based on the earlier series for dual stack TCP sockets.
David Gibson (11):
udp: Also bind() connected ports for "splice" forwarding
udp: Separate tracking of inbound and outbound packet flows
udp: Always use sendto() rather than send() for forwarding spliced
packets
udp: Don't connect "forward" sockets for spliced flows
udp: Remove the @bound field from union udp_epoll_ref
udp: Split splice field in udp_epoll_ref into (mostly) independent
bits
udp: Don't create double sockets for -U port
udp: Re-use fixed bound sockets for packet forwarding when possible
udp: Don't explicitly track originating socket for spliced
"connections"
udp: Update UDP "connection" timestamps in both directions
udp: Simplify udp_sock_handler_splice
passt.h | 2 +
udp.c | 344 ++++++++++++++++++++++----------------------------------
udp.h | 16 ++-
3 files changed, 144 insertions(+), 218 deletions(-)
--
2.38.1