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
Subject: Re: [PATCH v5 0/5] tcp: use csum_iov() in tcp_update_check_tcp[4|6]()
Date: Wed, 2 Oct 2024 16:46:19 +0200	[thread overview]
Message-ID: <20241002164619.46e63900@elisabeth> (raw)
In-Reply-To: <20241002163238.1778ed19@elisabeth>

On Wed, 2 Oct 2024 16:32:38 +0200
Stefano Brivio <sbrivio@redhat.com> wrote:

> On Fri, 27 Sep 2024 15:53:44 +0200
> Laurent Vivier <lvivier@redhat.com> wrote:
> 
> > For vhost-user, we will need to spread TCP payload over
> > several buffers. To re-use tcp_update_check_tcp[4|6](),
> > provide an iovec rather than a pointer to a buffer.
> > 
> > This series updates also csum_iov() and pcap_iov() to
> > add an offset of bytes to skip in the iovec array.
> > 
> > It's based on top of "tcp: Use tcp_payload_t rather than tcphdr" that
> > is added in the series for convenience.
> > 
> > v3 adds "udp: Update UDP checksum using an iovec array" that modifies
> > csum_udp4() and csum_udp6() in the same way.
> > 
> > Laurent Vivier (5):
> >   tcp: Use tcp_payload_t rather than tcphdr
> >   pcap: Add an offset argument in pcap_iov()
> >   checksum: Add an offset argument in csum_iov()
> >   tcp: Update TCP checksum using an iovec array
> >   udp: Update UDP checksum using an iovec array  
> 
> I *think* something in this series causes two test failures.
> 
> I wasn't able to reproduce them without this series (tried five times),
> but I don't always reproduce them with it (tried about 10 times, I
> didn't get any failure for 3 runs, one or both in the other runs).
> 
> The first one looks like this (copy and paste to a buffer to see it):

Grr, never mind, this seem to be caused by "[PATCH v3 0/4] Don't expose
container loopback services to the host" or something that came before.

I'll now re-test a few times both series separately and report back.

-- 
Stefano


      reply	other threads:[~2024-10-02 14:46 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-27 13:53 [PATCH v5 0/5] tcp: use csum_iov() in tcp_update_check_tcp[4|6]() Laurent Vivier
2024-09-27 13:53 ` [PATCH v5 1/5] tcp: Use tcp_payload_t rather than tcphdr Laurent Vivier
2024-09-27 13:53 ` [PATCH v5 2/5] pcap: Add an offset argument in pcap_iov() Laurent Vivier
2024-09-27 13:53 ` [PATCH v5 3/5] checksum: Add an offset argument in csum_iov() Laurent Vivier
2024-09-30  2:51   ` David Gibson
2024-09-27 13:53 ` [PATCH v5 4/5] tcp: Update TCP checksum using an iovec array Laurent Vivier
2024-09-30  2:56   ` David Gibson
2024-10-01  7:29   ` Stefano Brivio
2024-10-01 18:22     ` Stefano Brivio
2024-10-02  7:39       ` Laurent Vivier
2024-10-02  9:00         ` Stefano Brivio
2024-10-03 12:58           ` Laurent Vivier
2024-09-27 13:53 ` [PATCH v5 5/5] udp: Update UDP " Laurent Vivier
2024-09-30  2:58   ` David Gibson
2024-10-02 14:32 ` [PATCH v5 0/5] tcp: use csum_iov() in tcp_update_check_tcp[4|6]() Stefano Brivio
2024-10-02 14:46   ` Stefano Brivio [this message]

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=20241002164619.46e63900@elisabeth \
    --to=sbrivio@redhat.com \
    --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).