public inbox for passt-dev@passt.top
 help / color / mirror / code / Atom feed
From: Stefano Brivio <sbrivio@redhat.com>
To: Laurent Vivier <lvivier@redhat.com>
Cc: passt-dev@passt.top, David Gibson <david@gibson.dropbear.id.au>
Subject: Re: [PATCH v6 1/8] tcp: extract buffer management from tcp_send_flag()
Date: Thu, 13 Jun 2024 12:49:54 +0200	[thread overview]
Message-ID: <20240613124954.0134e128@elisabeth> (raw)
In-Reply-To: <79e33c3e-1194-4acb-b1ab-71d1ac6d94a7@redhat.com>

On Thu, 13 Jun 2024 12:22:54 +0200
Laurent Vivier <lvivier@redhat.com> wrote:

> On 13/06/2024 12:14, Stefano Brivio wrote:
> > On Thu, 13 Jun 2024 10:24:11 +0200
> > Laurent Vivier <lvivier@redhat.com> wrote:
> >   
> >> Hi,
> >>
> >> I think the problem can be because tcp_l2_buf_fill_headers() has been moved out of
> >> tcp_prepare_flags() and so moved after:
> >>
> >>           if (th->fin || th->syn)
> >>                   conn->seq_to_tap++;
> >>
> >> and con->seq_to_tap is also a parameter of tcp_l2_buf_fill_headers(). So it is increased
> >> before and not after.
> >>
> >> Could you try:
> >>
> >> diff --git a/tcp.c b/tcp.c
> >> index 6800209d4122..647f42291fcf 100644
> >> --- a/tcp.c
> >> +++ b/tcp.c
> >> @@ -1607,6 +1607,7 @@ static int tcp_prepare_flags(struct ctx *c, struct tcp_tap_conn *conn,
> >>           if (!tcp_update_seqack_wnd(c, conn, flags, &tinfo) && !flags)
> >>                   return 0;
> >>
> >> +       *optlen = 0;
> >>           if (flags & SYN) {
> >>                   int mss;
> >>
> >> @@ -1643,7 +1644,6 @@ static int tcp_prepare_flags(struct ctx *c, struct tcp_tap_conn *conn,
> >>                   *data++ = conn->ws_to_tap;
> >>           } else if (!(flags & RST)) {
> >>                   flags |= ACK;
> >> -               *optlen = 0;
> >>           }
> >>
> >>           th->doff = (sizeof(*th) + *optlen) / 4;
> >> @@ -1663,10 +1663,6 @@ static int tcp_prepare_flags(struct ctx *c, struct tcp_tap_conn *conn,
> >>           if (th->fin)
> >>                   conn_flag(c, conn, ACK_FROM_TAP_DUE);
> >>
> >> -       /* RFC 793, 3.1: "[...] and the first data octet is ISN+1." */
> >> -       if (th->fin || th->syn)
> >> -               conn->seq_to_tap++;
> >> -
> >>           return 1;
> >>    }
> >>
> >> @@ -1702,6 +1698,10 @@ static int tcp_send_flag(struct ctx *c, struct tcp_tap_conn *conn,
> >> int flags)
> >>                                           conn->seq_to_tap);
> >>           iov[TCP_IOV_PAYLOAD].iov_len = l4len;
> >>
> >> +       /* RFC 793, 3.1: "[...] and the first data octet is ISN+1." */
> >> +       if (th->fin || th->syn)
> >> +               conn->seq_to_tap++;
> >> +
> >>           if (flags & DUP_ACK) {
> >>                   struct iovec *dup_iov;
> >>                   int i;  
> > 
> > Ah, yes, good catch, I missed this one! It works. Note that it needs to
> > be:
> > 
> > 	if ((flags & FIN) || (flags & SYN))
> > 		...
> > 
> > because we don't have a TCP header there, yet.
> >   
> 
> I'm wondering if I can do:
> 
> +       seq = conn->seq_to_tap;
>          ret = tcp_prepare_flags(c, conn, flags, &payload->th,
>                                  payload->opts, &optlen);
>          if (ret <= 0)
>                  return ret;
> 
>          l4len = tcp_l2_buf_fill_headers(c, conn, iov, optlen, NULL,
> -                                       conn->seq_to_tap);
> +                                       seq);
> 
> to keep  the flags in tcp_prepare_flags()?

Maybe, yes. I don't really have a strong preference. On the other hand
tcp_send_flag() has to deal with the DUP_ACK case on its own anyway.

But sure, this version would be a bit cleaner, and if vhost-user code
will then want to call tcp_prepare_flags() without tcp_send_flag(),
it avoids code duplication, I guess?

-- 
Stefano


  reply	other threads:[~2024-06-13 10:50 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-12 15:47 [PATCH v6 0/8] Add vhost-user support to passt (part 2) Laurent Vivier
2024-06-12 15:47 ` [PATCH v6 1/8] tcp: extract buffer management from tcp_send_flag() Laurent Vivier
2024-06-12 21:22   ` Stefano Brivio
2024-06-13  6:07     ` Stefano Brivio
2024-06-13  8:24       ` Laurent Vivier
2024-06-13 10:14         ` Stefano Brivio
2024-06-13 10:22           ` Laurent Vivier
2024-06-13 10:49             ` Stefano Brivio [this message]
2024-06-13 10:58               ` Laurent Vivier
2024-06-13  7:31     ` Laurent Vivier
2024-06-13  9:35       ` Stefano Brivio
2024-06-13 14:36         ` David Gibson
2024-06-12 15:47 ` [PATCH v6 2/8] tcp: move buffers management functions to their own file Laurent Vivier
2024-06-12 15:54   ` Stefano Brivio
2024-06-12 15:47 ` [PATCH v6 3/8] tap: refactor packets handling functions Laurent Vivier
2024-06-12 15:52   ` Stefano Brivio
2024-06-12 16:00     ` Laurent Vivier
2024-06-12 15:47 ` [PATCH v6 4/8] udp: refactor UDP header update functions Laurent Vivier
2024-06-12 15:47 ` [PATCH v6 5/8] udp: rename udp_sock_handler() to udp_buf_sock_handler() Laurent Vivier
2024-06-12 15:47 ` [PATCH v6 6/8] vhost-user: compare mode MODE_PASTA and not MODE_PASST Laurent Vivier
2024-06-12 15:47 ` [PATCH v6 7/8] iov: remove iov_copy() Laurent Vivier
2024-06-12 15:47 ` [PATCH v6 8/8] tap: use in->buf_size rather than sizeof(pkt_buf) Laurent Vivier
2024-06-12 17:16 ` [PATCH v6 0/8] Add vhost-user support to passt (part 2) Stefano Brivio
2024-06-12 17:37   ` Stefano Brivio
2024-06-12 21:23     ` 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=20240613124954.0134e128@elisabeth \
    --to=sbrivio@redhat.com \
    --cc=david@gibson.dropbear.id.au \
    --cc=lvivier@redhat.com \
    --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).