From: Stefano Brivio <sbrivio@redhat.com>
To: David Gibson <david@gibson.dropbear.id.au>
Cc: passt-dev@passt.top
Subject: Re: [PATCH 5/8] udp: Pre-populate msg_names with local address
Date: Tue, 13 Dec 2022 23:48:52 +0100 [thread overview]
Message-ID: <20221213234852.31c05833@elisabeth> (raw)
In-Reply-To: <20221205081425.2614425-6-david@gibson.dropbear.id.au>
On Mon, 5 Dec 2022 19:14:22 +1100
David Gibson <david@gibson.dropbear.id.au> wrote:
> udp_splice_namebuf is now used only for spliced sending, and so it only
> ever populated with the localhost address, either IPv4 or IPv6. So,
> replace the awkward initialization in udp_sock_handler_splice() with
> statically initialized versions for IPv4 and IPv6. We then just need to
> update the port number in udp_sock_handler_splice().
>
> Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
> ---
> udp.c | 40 ++++++++++++++++++----------------------
> util.h | 7 +++++++
> 2 files changed, 25 insertions(+), 22 deletions(-)
>
> diff --git a/udp.c b/udp.c
> index 24fa984..7c601cc 100644
> --- a/udp.c
> +++ b/udp.c
> @@ -232,11 +232,18 @@ static struct mmsghdr udp4_l2_mh_tap [UDP_MAX_FRAMES];
> static struct mmsghdr udp6_l2_mh_tap [UDP_MAX_FRAMES];
>
> /* recvmmsg()/sendmmsg() data for "spliced" connections */
> -static struct sockaddr_storage udp_splice_namebuf;
> -
> static struct iovec udp4_iov_splice [UDP_MAX_FRAMES];
> static struct iovec udp6_iov_splice [UDP_MAX_FRAMES];
>
> +static struct sockaddr_in udp_localname4 = {
> + .sin_family = AF_INET,
> + .sin_addr = IN4ADDR_LOOPBACK_INIT,
> +};
> +static struct sockaddr_in6 udp_localname6 = {
> + .sin6_family = AF_INET6,
> + .sin6_addr = IN6ADDR_LOOPBACK_INIT,
> +};
Nit, not a strong preference and not worth re-spinning just for this: I
think udp4_localname and udp6_localname would be more consistent with
everything else here, hence easier to type without double checking.
--
Stefano
next prev parent reply other threads:[~2022-12-13 22:48 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-05 8:14 [PATCH 0/8] Don't use additional sockets for receiving "spliced" UDP communications David Gibson
2022-12-05 8:14 ` [PATCH 1/8] udp: Move sending pasta tap frames to the end of udp_sock_handler() David Gibson
2022-12-05 8:14 ` [PATCH 2/8] udp: Split sending to passt tap interface into separate function David Gibson
2022-12-05 8:14 ` [PATCH 3/8] udp: Split receive from preparation and send in udp_sock_handler() David Gibson
2022-12-05 8:14 ` [PATCH 4/8] udp: Receive multiple datagrams at once on the pasta sock->tap path David Gibson
2022-12-13 22:48 ` Stefano Brivio
2022-12-14 1:42 ` David Gibson
2022-12-14 10:35 ` Stefano Brivio
2022-12-20 10:42 ` Stefano Brivio
2022-12-21 6:00 ` David Gibson
2022-12-22 2:37 ` Stefano Brivio
2023-01-04 0:08 ` Stefano Brivio
2023-01-04 4:53 ` David Gibson
2022-12-05 8:14 ` [PATCH 5/8] udp: Pre-populate msg_names with local address David Gibson
2022-12-13 22:48 ` Stefano Brivio [this message]
2022-12-14 1:22 ` David Gibson
2022-12-05 8:14 ` [PATCH 6/8] udp: Unify udp_sock_handler_splice() with udp_sock_handler() David Gibson
2022-12-13 22:48 ` Stefano Brivio
2022-12-14 1:19 ` David Gibson
2022-12-14 10:35 ` Stefano Brivio
2022-12-05 8:14 ` [PATCH 7/8] udp: Decide whether to "splice" per datagram rather than per socket David Gibson
2022-12-13 22:49 ` Stefano Brivio
2022-12-14 1:47 ` David Gibson
2022-12-14 10:35 ` Stefano Brivio
2022-12-15 0:33 ` David Gibson
2022-12-05 8:14 ` [PATCH 8/8] udp: Don't use separate sockets to listen for spliced packets David Gibson
2022-12-06 6:45 ` [PATCH 0/8] Don't use additional sockets for receiving "spliced" UDP communications Stefano Brivio
2022-12-06 6:46 ` Stefano Brivio
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=20221213234852.31c05833@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).