From: David Gibson <david@gibson.dropbear.id.au>
To: Jon Maloy <jmaloy@redhat.com>
Cc: passt-dev@passt.top, sbrivio@redhat.com, lvivier@redhat.com,
dgibson@redhat.com
Subject: Re: [PATCH v5 0/2] tcp: unify IPv4 and IPv6 tap queues
Date: Tue, 29 Oct 2024 15:11:51 +1100 [thread overview]
Message-ID: <ZyBgh4Rvrt32XQd5@zatzit> (raw)
In-Reply-To: <20241029021400.784052-1-jmaloy@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 955 bytes --]
On Mon, Oct 28, 2024 at 10:13:58PM -0400, Jon Maloy wrote:
> This should save us some memory and code.
LGTM. I'll rebase my IOV re-orgs on top of these.
>
> ---
> v2: - Setting pointers to pre-set IP and MAC headers on the fly
> instead of copying them.
> - Merged patch #2 and #3 from v1
> v3: - Changes based on feedback from team
> v4: - Rebased
> v5: - Changes based on feedback from team and rebased
>
> Jon Maloy (2):
> tcp: set ip and eth headers in l2 tap queues on the fly
> tcp: unify l2 TCPv4 and TCPv6 queues and structures
>
> tcp.c | 6 +-
> tcp_buf.c | 272 ++++++++++++++++++------------------------------------
> tcp_buf.h | 3 +-
> 3 files changed, 91 insertions(+), 190 deletions(-)
>
--
David Gibson (he or they) | I'll have my music baroque, and my code
david AT gibson.dropbear.id.au | minimalist, thank you, not the other way
| around.
http://www.ozlabs.org/~dgibson
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2024-10-29 4:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-29 2:13 [PATCH v5 0/2] tcp: unify IPv4 and IPv6 tap queues Jon Maloy
2024-10-29 2:13 ` [PATCH v5 1/2] tcp: set ip and eth headers in l2 tap queues on the fly Jon Maloy
2024-10-29 4:11 ` David Gibson
2024-10-29 2:14 ` [PATCH v5 2/2] tcp: unify l2 TCPv4 and TCPv6 queues and structures Jon Maloy
2024-10-29 4:11 ` David Gibson [this message]
2024-10-29 13:57 ` [PATCH v5 0/2] tcp: unify IPv4 and IPv6 tap queues Stefano Brivio
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=ZyBgh4Rvrt32XQd5@zatzit \
--to=david@gibson.dropbear.id.au \
--cc=dgibson@redhat.com \
--cc=jmaloy@redhat.com \
--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).