public inbox for passt-dev@passt.top
 help / color / mirror / code / Atom feed
From: David Gibson <david@gibson.dropbear.id.au>
To: Stefano Brivio <sbrivio@redhat.com>, passt-dev@passt.top
Cc: Laurent Vivier <lvivier@redhat.com>,
	David Gibson <david@gibson.dropbear.id.au>
Subject: [PATCH 0/7] Small improvements to IOV handling
Date: Mon, 29 Apr 2024 17:09:26 +1000	[thread overview]
Message-ID: <20240429070933.1366881-1-david@gibson.dropbear.id.au> (raw)

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 7/7 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.

David Gibson (7):
  checksum: Use proto_ipv6_header_psum() for ICMPv6 as well
  tap: Split tap specific and L2 (ethernet) headers
  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]()

 checksum.c |  46 ++++++++---------
 checksum.h |  10 ++--
 icmp.c     |   8 +--
 iov.h      |   3 ++
 passt.h    |   4 +-
 tap.c      |  51 ++++++++++---------
 tap.h      |  46 +++++++++++++----
 tcp.c      | 144 +++++++++++++++++++++++------------------------------
 udp.c      |  50 ++++++++++---------
 9 files changed, 184 insertions(+), 178 deletions(-)

-- 
2.44.0


             reply	other threads:[~2024-04-29  7:09 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-29  7:09 David Gibson [this message]
2024-04-29  7:09 ` [PATCH 1/7] checksum: Use proto_ipv6_header_psum() for ICMPv6 as well David Gibson
2024-04-29  7:09 ` [PATCH 2/7] tap: Split tap specific and L2 (ethernet) headers David Gibson
2024-04-30 18:46   ` Stefano Brivio
2024-04-30 23:53     ` David Gibson
2024-04-29  7:09 ` [PATCH 3/7] treewide: Standardise variable names for various packet lengths David Gibson
2024-04-30 18:46   ` Stefano Brivio
2024-05-01  0:05     ` David Gibson
2024-04-29  7:09 ` [PATCH 4/7] tcp: Simplify packet length calculation when preparing headers David Gibson
2024-04-29  7:09 ` [PATCH 5/7] tap, tcp: (Re-)abstract TAP specific header handling David Gibson
2024-04-30 18:47   ` Stefano Brivio
2024-05-01  0:06     ` David Gibson
2024-04-29  7:09 ` [PATCH 6/7] iov: Helper macro to construct iovs covering existing variables or fields David Gibson
2024-04-30 18:47   ` Stefano Brivio
2024-05-01  0:09     ` David Gibson
2024-04-29  7:09 ` [PATCH 7/7] tcp: Update tap specific header too in tcp_fill_headers[46]() David Gibson
2024-04-30 18:48   ` Stefano Brivio
2024-05-01  0:10     ` 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=20240429070933.1366881-1-david@gibson.dropbear.id.au \
    --to=david@gibson.dropbear.id.au \
    --cc=lvivier@redhat.com \
    --cc=passt-dev@passt.top \
    --cc=sbrivio@redhat.com \
    /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).