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>,
	Laurent Vivier <lvivier@redhat.com>,
	passt-dev@passt.top
Cc: David Gibson <david@gibson.dropbear.id.au>
Subject: [PATCH 0/7] Rework some IOV handling in TCP code
Date: Mon, 28 Oct 2024 20:40:43 +1100	[thread overview]
Message-ID: <20241028094050.1609090-1-david@gibson.dropbear.id.au> (raw)

These reworks are largely aimed at making the vhost-user integration
easier, and with luck allowing more logic to be shared between it and
the existing "buffer" paths.  Of course, in the short term, these will
probably conflict with the patches... I hope it ends up as a net
positive, Laurent, let me know.

I think a number of similar changes should be possible for UDP, but I
haven't tackled that yet.

David Gibson (7):
  tcp: Pass TCP header and payload separately to
    tcp_update_check_tcp[46]()
  tcp: Move tcp_l2_buf_fill_headers() to tcp_buf.c
  tcp: Rework tcp_l2_buf_fill_headers() into tcp_buf_make_frame()
  tcp: Don't use return value from tcp_fill_headers[46] to adjust
    iov_len
  tcp: Pass TCP header and payload separately to tcp_fill_headers[46]()
  tcp: Merge tcp_update_check_tcp[46]()
  tcp: Fold tcp_update_csum() into tcp_fill_header()

 tcp.c          | 232 +++++++++++--------------------------------------
 tcp_buf.c      |  48 +++++++---
 tcp_internal.h |  15 +++-
 3 files changed, 100 insertions(+), 195 deletions(-)

-- 
2.47.0


             reply	other threads:[~2024-10-28  9:41 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-28  9:40 David Gibson [this message]
2024-10-28  9:40 ` [PATCH 1/7] tcp: Pass TCP header and payload separately to tcp_update_check_tcp[46]() David Gibson
2024-10-28 18:42   ` Stefano Brivio
2024-10-29  3:02     ` David Gibson
2024-10-29  4:07       ` David Gibson
2024-10-29  9:09         ` Stefano Brivio
2024-10-29  9:26           ` David Gibson
2024-10-29 10:32             ` Stefano Brivio
2024-10-28  9:40 ` [PATCH 2/7] tcp: Move tcp_l2_buf_fill_headers() to tcp_buf.c David Gibson
2024-10-28  9:40 ` [PATCH 3/7] tcp: Rework tcp_l2_buf_fill_headers() into tcp_buf_make_frame() David Gibson
2024-10-28  9:40 ` [PATCH 4/7] tcp: Don't use return value from tcp_fill_headers[46] to adjust iov_len David Gibson
2024-10-28  9:40 ` [PATCH 5/7] tcp: Pass TCP header and payload separately to tcp_fill_headers[46]() David Gibson
2024-10-28  9:40 ` [PATCH 6/7] tcp: Merge tcp_update_check_tcp[46]() David Gibson
2024-10-28  9:40 ` [PATCH 7/7] tcp: Fold tcp_update_csum() into tcp_fill_header() 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=20241028094050.1609090-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).