public inbox for passt-dev@passt.top
 help / color / mirror / code / Atom feed
From: Stefano Brivio <sbrivio@redhat.com>
To: David Gibson <david@gibson.dropbear.id.au>
Cc: passt-dev@passt.top
Subject: Re: [PATCH 03/12] udp: Polish udp_vu_sock_info() and remove from vu specific code
Date: Mon, 7 Apr 2025 23:49:18 +0200	[thread overview]
Message-ID: <20250407234918.1b53503e@elisabeth> (raw)
In-Reply-To: <20250404101542.3729316-4-david@gibson.dropbear.id.au>

On Fri,  4 Apr 2025 21:15:33 +1100
David Gibson <david@gibson.dropbear.id.au> wrote:

> udp_vu_sock_info() uses MSG_PEEK to look ahead at the next datagram to be
> received and gets its source address.  Currently we only use it in the
> vhost-user path, but there's nothing inherently vhost-user specific about
> it.  We have upcoming uses for it elsewhere so rename and move to udp.c.
> 
> While we're there, polish its error reporting a litle.
> 
> Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
> ---
>  udp.c          | 25 +++++++++++++++++++++++++
>  udp_internal.h |  1 +
>  udp_vu.c       | 19 +------------------
>  3 files changed, 27 insertions(+), 18 deletions(-)
> 
> diff --git a/udp.c b/udp.c
> index 8125cfcb..6b72c30f 100644
> --- a/udp.c
> +++ b/udp.c
> @@ -629,6 +629,31 @@ static int udp_sock_errs(const struct ctx *c, union epoll_ref ref)
>  	return n_err;
>  }
>  
> +/**
> + * udp_peek_addr() - Get source address for next packet
> + * @s:		Socket to get information from
> + * @src:	Socket address (output)
> + *
> + * Return: 0 on success, -1 otherwise
> + */
> +int udp_peek_addr(int s, union sockaddr_inany *src)
> +{
> +	struct msghdr msg = {
> +		.msg_name = src,
> +		.msg_namelen = sizeof(*src),
> +	};
> +	int rc;
> +
> +	rc = recvmsg(s, &msg, MSG_PEEK | MSG_DONTWAIT);
> +	if (rc < 0) {
> +		if (errno != EAGAIN && errno != EWOULDBLOCK)
> +			warn_perror("Error peeking at socket address");
> +		return rc;
> +	}
> +	return 0;
> +}
> +
> +
>  /**

Excess newline. Fixed on merge.

>   * udp_sock_recv() - Receive datagrams from a socket
>   * @c:		Execution context

-- 
Stefano


  reply	other threads:[~2025-04-07 21:49 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-04 10:15 [PATCH 00/12] Use connect()ed sockets for both sides of UDP flows David Gibson
2025-04-04 10:15 ` [PATCH 01/12] udp: Use connect()ed sockets for initiating side David Gibson
2025-04-04 10:15 ` [PATCH 02/12] udp: Make udp_sock_recv() take max number of frames as a parameter David Gibson
2025-04-07 21:49   ` Stefano Brivio
2025-04-04 10:15 ` [PATCH 03/12] udp: Polish udp_vu_sock_info() and remove from vu specific code David Gibson
2025-04-07 21:49   ` Stefano Brivio [this message]
2025-04-04 10:15 ` [PATCH 04/12] udp: Don't bother to batch datagrams from "listening" socket David Gibson
2025-04-04 10:15 ` [PATCH 05/12] udp: Parameterize number of datagrams handled by udp_*_reply_sock_data() David Gibson
2025-04-04 10:15 ` [PATCH 06/12] udp: Split spliced forwarding path from udp_buf_reply_sock_data() David Gibson
2025-04-07 21:49   ` Stefano Brivio
2025-04-04 10:15 ` [PATCH 07/12] udp: Merge vhost-user and "buf" listening socket paths David Gibson
2025-04-04 10:15 ` [PATCH 08/12] udp: Move UDP_MAX_FRAMES to udp.c David Gibson
2025-04-04 10:15 ` [PATCH 09/12] udp_flow: Take pif and port as explicit parameters to udp_flow_from_sock() David Gibson
2025-04-07 21:49   ` Stefano Brivio
2025-04-04 10:15 ` [PATCH 10/12] udp: Rework udp_listen_sock_data() into udp_sock_fwd() David Gibson
2025-04-04 10:15 ` [PATCH 11/12] udp: Fold udp_splice_prepare and udp_splice_send into udp_sock_to_sock David Gibson
2025-04-07 21:49   ` Stefano Brivio
2025-04-04 10:15 ` [PATCH 12/12] udp_flow: Don't discard packets that arrive between bind() and connect() David Gibson
2025-04-07 21:49   ` Stefano Brivio
2025-04-07 21:49 ` [PATCH 00/12] Use connect()ed sockets for both sides of UDP flows Stefano Brivio
2025-04-07 23:50   ` David Gibson

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=20250407234918.1b53503e@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).