From: Stefano Brivio <sbrivio@redhat.com>
To: Laurent Vivier <lvivier@redhat.com>
Cc: passt-dev@passt.top
Subject: Re: [PATCH v6 0/5] tcp: use csum_iov() in tcp_update_check_tcp[4|6]()
Date: Fri, 4 Oct 2024 15:10:53 +0200 [thread overview]
Message-ID: <20241004151053.3e76478d@elisabeth> (raw)
In-Reply-To: <20241003145108.2227355-1-lvivier@redhat.com>
On Thu, 3 Oct 2024 16:51:03 +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.
>
> v6: update tcp.c with fix for clang-tidy error and add missing static
>
> 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 ran tests a few times with just this series, no failures observed.
Applied, sorry for the delay.
--
Stefano
prev parent reply other threads:[~2024-10-04 13:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-03 14:51 [PATCH v6 0/5] tcp: use csum_iov() in tcp_update_check_tcp[4|6]() Laurent Vivier
2024-10-03 14:51 ` [PATCH v6 1/5] tcp: Use tcp_payload_t rather than tcphdr Laurent Vivier
2024-10-03 14:51 ` [PATCH v6 2/5] pcap: Add an offset argument in pcap_iov() Laurent Vivier
2024-10-03 14:51 ` [PATCH v6 3/5] checksum: Add an offset argument in csum_iov() Laurent Vivier
2024-10-03 14:51 ` [PATCH v6 4/5] tcp: Update TCP checksum using an iovec array Laurent Vivier
2024-10-03 14:55 ` Laurent Vivier
2024-10-04 6:56 ` Stefano Brivio
2024-10-03 14:51 ` [PATCH v6 5/5] udp: Update UDP " Laurent Vivier
2024-10-04 13:10 ` 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=20241004151053.3e76478d@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).