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 6/8] tcp_splice: Simplify / correct OUT_WAIT flag handling
Date: Thu, 04 Jun 2026 06:41:37 +0200 (CEST)	[thread overview]
Message-ID: <20260604064134.478745ed@elisabeth> (raw)
In-Reply-To: <20260528050213.679685-7-david@gibson.dropbear.id.au>

On Thu, 28 May 2026 15:02:11 +1000
David Gibson <david@gibson.dropbear.id.au> wrote:

> We set the OUT_WAIT flag if we stop forwarding due to EAGAIN, but there's
> still data in the pipe.  That ensures we wake up when the output socket has
> room to drain the pipe into.
> 
> We clear the OUT_WAIT flag when we complete forwarding on an EPOLLOUT
> event, but that's not quite right.  Even though it's called on an EPOLLOUT,
> tcp_splice_forward() could, in principle empty the pipe, but also read
> enough new data from the other side to fill it again.  That would set
> OUT_WAIT internally, but it would be cleared after returning meaning
> we could miss a necessary wakeup.

The current logic in tcp_splice_sock_handler():

	if (events & EPOLLOUT) {
		if (tcp_splice_forward(c, conn, !evsidei, now))
			goto reset;
		conn_event(conn, ~OUT_WAIT(evsidei));
	}

	if (events & EPOLLIN) {
		if (tcp_splice_forward(c, conn, evsidei, now))
			goto reset;
	}

would prevent the case you described, because if we read new data from
the other side filling the pipe, we'll hit (events & EPOLLIN) and set
OUT_WAIT again if needed.

But there's a case this should actually fix, even though I've never
seen it happening in practice: what if we *don't* read new data from
the other side, and we can't empty the pipe in one EPOLLOUT shot anyway?

I hadn't considered that before but if the receiver is slow enough
that's probably possible.

> The condition on whether we need write side wakeups is actually fairly
> simple: we need them if and only if we return to the main loop with data
> in the pipe.  Maintain that in a single place - right after we exit the
> forwarding loop in tcp_splice_forward().
> 
> Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
> ---
>  tcp_splice.c | 16 +++++++++-------
>  1 file changed, 9 insertions(+), 7 deletions(-)
> 
> diff --git a/tcp_splice.c b/tcp_splice.c
> index 42902684..5f412584 100644
> --- a/tcp_splice.c
> +++ b/tcp_splice.c
> @@ -531,19 +531,22 @@ static int tcp_splice_forward(struct ctx *c,
>  		conn->pending[fromsidei] += readlen > 0 ? readlen : 0;
>  		conn->pending[fromsidei] -= written > 0 ? written : 0;
>  
> -		if (written < 0) {
> -			if (!conn->pending[fromsidei])
> -				break;
> -
> -			conn_event(conn, OUT_WAIT(!fromsidei));
> +		if (written < 0)
>  			break;
> -		}
>  
>  		if (conn->events & FIN_RCVD(fromsidei) &&
>  		    !conn->pending[fromsidei])
>  			break;
>  	}
>  
> +	/* We need write-side wakeups if and only if we have data in the pipe to
> +	 * drain.
> +	 */
> +	if (conn->pending[fromsidei])
> +		conn_event(conn, OUT_WAIT(!fromsidei));
> +	else
> +		conn_event(conn, ~OUT_WAIT(!fromsidei));
> +
>  	if ((conn->events & FIN_RCVD(fromsidei)) &&
>  	    !(conn->events & FIN_SENT(!fromsidei)) &&
>  	    !conn->pending[fromsidei]) {
> @@ -606,7 +609,6 @@ void tcp_splice_sock_handler(struct ctx *c, union epoll_ref ref,
>  	if (events & EPOLLOUT) {
>  		if (tcp_splice_forward(c, conn, !evsidei, now))
>  			goto reset;
> -		conn_event(conn, ~OUT_WAIT(evsidei));
>  	}
>  
>  	if (events & (EPOLLIN | EPOLLRDHUP)) {

-- 
Stefano


  reply	other threads:[~2026-06-04  4:41 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-28  5:02 [PATCH 0/8] splice() forwarding cleanups David Gibson
2026-05-28  5:02 ` [PATCH 1/8] tcp_splice: Remove never-invoked SO_RCVLOWAT logic David Gibson
2026-05-28  5:02 ` [PATCH 2/8] tcp_splice: Simplify EPOLLRDHUP / eof / FIN handling David Gibson
2026-05-28  5:02 ` [PATCH 3/8] tcp_splice: Improve EOF exit condition for the loop David Gibson
2026-05-28  5:02 ` [PATCH 4/8] tcp_splice: Remove goto from forwarding loop David Gibson
2026-05-28  5:02 ` [PATCH 5/8] tcp_splice: Simplify shutdown(2) handling David Gibson
2026-05-28  5:02 ` [PATCH 6/8] tcp_splice: Simplify / correct OUT_WAIT flag handling David Gibson
2026-06-04  4:41   ` Stefano Brivio [this message]
2026-06-04  5:14     ` David Gibson
2026-05-28  5:02 ` [PATCH 7/8] tcp_splice: Remove questionable "optimisation" of pending bytes tracking David Gibson
2026-06-04  4:41   ` Stefano Brivio
2026-06-04  5:14     ` David Gibson
2026-05-28  5:02 ` [PATCH 8/8] tcp_splice: Exit forwarding earlier when stalled read side David Gibson
2026-06-04  4:41   ` Stefano Brivio
2026-06-04  5:26     ` David Gibson
2026-06-04  5:44       ` Stefano Brivio
2026-06-04  7:08         ` 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=20260604064134.478745ed@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).