public inbox for passt-dev@passt.top
 help / color / mirror / code / Atom feed
From: Jon Maloy <jmaloy@redhat.com>
To: passt-dev@passt.top, Stefano Brivio <sbrivio@redhat.com>,
	David Gibson <dgibson@redhat.com>,
	Laurent Vivier <lvivier@redhat.com>
Subject: Re: [RFC v2] tcp: add support for read with offset when using MSG_PEEK
Date: Thu, 22 Jun 2023 22:36:49 -0400	[thread overview]
Message-ID: <d497542c-c0df-2877-276f-26982af47055@redhat.com> (raw)
In-Reply-To: <20230623021227.2625490-1-jmaloy@redhat.com>

(Added <passt-dev@passt.top> to distribution list.

I found that my first approach was too simplistic, since it only moved 
the reading
area forward in the receive buffer, but continue to fill in iov[0] with 
the indicated
length.
This commit exactly what we want: we indicate a NULL pointer in iov[0], but
want the actually read bytes to end up in the remaining entries, and also
the returned value to indicate the actually read length.

I look forward to feedback to this, then I can hopefully post it to the 
netdev
list next week.

///jon


On 2023-06-22 22:12, Jon Maloy wrote:
> When reading received messages with MSG_PEEK, we sometines have to read
> the leading bytes of the stream several times, only to reach the bytes
> we really want. This is clearly non-optimal.
>
> What we would want is something similar to pread/preadv(), but working
> even for tcp sockets. At the same time, we obviously don't want to add
> any new arguments to the recv/recvmsg() calls.
>
> In this commit, we allow the user to set iovec.iov_base in the first
> vector entry to NULL. This tells the socket to skip the first entry,
> hence making the iov_len field of that entry indicate the offset value.
> This way, there is no need to add any new arguments.
>
> This change is simple and non-intrusive, and should be safe addition to
> the socket API. We have measured it to give a throughput improvement of
> 8-10 % for the protocol splicer 'passst', which is used in KubeVirt
> containers.
>
> Signed-off-by: Jon Maloy <jmaloy@redhat.com>
>
> works with original msghdr
>
> Signed-off-by: Jon Maloy <jmaloy@redhat.com>
> ---
>   net/ipv4/tcp.c | 10 +++++++++-
>   1 file changed, 9 insertions(+), 1 deletion(-)
>
> diff --git a/net/ipv4/tcp.c b/net/ipv4/tcp.c
> index 33f559f491c8..1d89337e89b6 100644
> --- a/net/ipv4/tcp.c
> +++ b/net/ipv4/tcp.c
> @@ -2428,6 +2428,7 @@ static int tcp_recvmsg_locked(struct sock *sk, struct msghdr *msg, size_t len,
>   	struct tcp_sock *tp = tcp_sk(sk);
>   	int copied = 0;
>   	u32 peek_seq;
> +	u32 peek_offset;
>   	u32 *seq;
>   	unsigned long used;
>   	int err;
> @@ -2435,7 +2436,6 @@ static int tcp_recvmsg_locked(struct sock *sk, struct msghdr *msg, size_t len,
>   	long timeo;
>   	struct sk_buff *skb, *last;
>   	u32 urg_hole = 0;
> -
>   	err = -ENOTCONN;
>   	if (sk->sk_state == TCP_LISTEN)
>   		goto out;
> @@ -2469,6 +2469,14 @@ static int tcp_recvmsg_locked(struct sock *sk, struct msghdr *msg, size_t len,
>   	if (flags & MSG_PEEK) {
>   		peek_seq = tp->copied_seq;
>   		seq = &peek_seq;
> +		if (msg->msg_iter.iov[0].iov_base == NULL) {
> +			peek_offset = msg->msg_iter.iov[0].iov_len;
> +			msg->msg_iter.iov = &msg->msg_iter.iov[1];
> +			msg->msg_iter.nr_segs -= 1;
> +			msg->msg_iter.count -= peek_offset;
> +			len -= peek_offset;
> +			*seq += peek_offset;
> +		}
>   	}
>   
>   	target = sock_rcvlowat(sk, flags & MSG_WAITALL, len);


  reply	other threads:[~2023-06-23  2:36 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-23  2:12 [RFC v2] tcp: add support for read with offset when using MSG_PEEK Jon Maloy
2023-06-23  2:36 ` Jon Maloy [this message]
2023-06-23 11:02 ` Stefano Brivio
2023-09-04 17:14   ` Jon Maloy
2023-09-05  2:16     ` David Gibson
2023-09-05  6:19       ` 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=d497542c-c0df-2877-276f-26982af47055@redhat.com \
    --to=jmaloy@redhat.com \
    --cc=dgibson@redhat.com \
    --cc=lvivier@redhat.com \
    --cc=passt-dev@passt.top \
    --cc=sbrivio@redhat.com \
    /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).