On Fri, 4 Apr 2025 21:15:30 +1100
David Gibson <david(a)gibson.dropbear.id.au> wrote:
As discussed, I've been working on using
connect()ed sockets, rather
than dups of the listening sockets for handling traffic on the
initiating side of UDP flows. This improves consistency, avoids some
problems (bug 103) and will allow for some useful future improvements.
It has the nice side effect of allowing some more code to be shared
between various paths, resulting in a pretty nice negative diffstat.
David Gibson (12):
udp: Use connect()ed sockets for initiating side
udp: Make udp_sock_recv() take max number of frames as a parameter
udp: Polish udp_vu_sock_info() and remove from vu specific code
udp: Don't bother to batch datagrams from "listening" socket
udp: Parameterize number of datagrams handled by
udp_*_reply_sock_data()
udp: Split spliced forwarding path from udp_buf_reply_sock_data()
udp: Merge vhost-user and "buf" listening socket paths
udp: Move UDP_MAX_FRAMES to udp.c
udp_flow: Take pif and port as explicit parameters to
udp_flow_from_sock()
udp: Rework udp_listen_sock_data() into udp_sock_fwd()
udp: Fold udp_splice_prepare and udp_splice_send into udp_sock_to_sock
udp_flow: Don't discard packets that arrive between bind() and
connect()
Applied. I took the liberty of fixing up a number of nits (all in
comments or outside functions), as that was all I had. I listed them as
comments to single patches.