From: Stefano Brivio <sbrivio@redhat.com>
To: David Gibson <david@gibson.dropbear.id.au>
Cc: passt-dev@passt.top, Laurent Vivier <lvivier@redhat.com>
Subject: Re: [PATCH v2 00/10] Small improvements to IOV handling
Date: Thu, 2 May 2024 16:52:20 +0200 [thread overview]
Message-ID: <20240502165220.6efcb349@elisabeth> (raw)
In-Reply-To: <20240501065353.1682358-1-david@gibson.dropbear.id.au>
On Wed, 1 May 2024 16:53:43 +1000
David Gibson <david@gibson.dropbear.id.au> wrote:
> Laurent's changes to split TCP buffers into various components with
> IOVs is now merged. This series has a batch of small cleanups to make
> the handling of this slightly nicer. These are preliminaries to doing
> something similar with the UDP buffers.
>
> Note that patch 10/10 might interfere with the experiments to work out
> what is going wrong with the odd batching / performance issues we've
> seen. We can leave it off for the time being if that's a problem.
I think it's quick to locally revert for tests if needed.
> Changes since v1:
> * Added new patch removing some unused structures
> * Added two new patches cleaning up some endianness confusion
> * Added a bunch of missing cases to standardisation of length
> variable names
> * Assorted minor revisions based on Stefano's review
>
> David Gibson (10):
> checksum: Use proto_ipv6_header_psum() for ICMPv6 as well
> tap: Split tap specific and L2 (ethernet) headers
> tap: Remove unused structs tap_msg, tap_l4_msg
> treewide: Remove misleading and redundant endianness notes
> checksum: Make csum_ip4_header() take a host endian length
> treewide: Standardise variable names for various packet lengths
> tcp: Simplify packet length calculation when preparing headers
> tap, tcp: (Re-)abstract TAP specific header handling
> iov: Helper macro to construct iovs covering existing variables or
> fields
> tcp: Update tap specific header too in tcp_fill_headers[46]()
Applied.
--
Stefano
prev parent reply other threads:[~2024-05-02 14:52 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-01 6:53 [PATCH v2 00/10] Small improvements to IOV handling David Gibson
2024-05-01 6:53 ` [PATCH v2 01/10] checksum: Use proto_ipv6_header_psum() for ICMPv6 as well David Gibson
2024-05-01 6:53 ` [PATCH v2 02/10] tap: Split tap specific and L2 (ethernet) headers David Gibson
2024-05-01 6:53 ` [PATCH v2 03/10] tap: Remove unused structs tap_msg, tap_l4_msg David Gibson
2024-05-01 6:53 ` [PATCH v2 04/10] treewide: Remove misleading and redundant endianness notes David Gibson
2024-05-01 6:53 ` [PATCH v2 05/10] checksum: Make csum_ip4_header() take a host endian length David Gibson
2024-05-01 6:53 ` [PATCH v2 06/10] treewide: Standardise variable names for various packet lengths David Gibson
2024-05-01 6:53 ` [PATCH v2 07/10] tcp: Simplify packet length calculation when preparing headers David Gibson
2024-05-01 6:53 ` [PATCH v2 08/10] tap, tcp: (Re-)abstract TAP specific header handling David Gibson
2024-05-01 6:53 ` [PATCH v2 09/10] iov: Helper macro to construct iovs covering existing variables or fields David Gibson
2024-05-01 6:53 ` [PATCH v2 10/10] tcp: Update tap specific header too in tcp_fill_headers[46]() David Gibson
2024-05-02 14:52 ` 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=20240502165220.6efcb349@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).