From: Stefano Brivio <sbrivio@redhat.com>
To: David Gibson <david@gibson.dropbear.id.au>
Cc: passt-dev@passt.top
Subject: Re: [PATCH v3 00/18] RFC: Unify and simplify tap send path
Date: Tue, 24 Jan 2023 22:20:43 +0100 [thread overview]
Message-ID: <20230124222043.281ef58c@elisabeth> (raw)
In-Reply-To: <20230106004322.985665-1-david@gibson.dropbear.id.au>
On Fri, 6 Jan 2023 11:43:04 +1100
David Gibson <david@gibson.dropbear.id.au> wrote:
> Although we have an abstraction for the "slow path" (DHCP, NDP) guest
> bound packets, the TCP and UDP forwarding paths write directly to the
> tap fd. However, it turns out how they send frames to the tap device
> is more similar than it originally appears.
>
> This series unifies the low-level tap send functions for TCP and UDP,
> and makes some clean ups along the way.
>
> This is based on my earlier outstanding series.
For some reason, performance tests consistently get stuck (both TCP and
UDP, sometimes throughput, sometimes latency tests) with this series,
and not without it, but I don't see any possible relationship with that.
I checked debug output and I couldn't find anything obviously wrong
there. I just started checking packet captures now...
--
Stefano
next prev parent reply other threads:[~2023-01-24 21:20 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-06 0:43 [PATCH v3 00/18] RFC: Unify and simplify tap send path David Gibson
2023-01-06 0:43 ` [PATCH v3 01/18] pcap: Introduce pcap_frame() helper David Gibson
2023-01-06 0:43 ` [PATCH v3 02/18] pcap: Replace pcapm() with pcap_multiple() David Gibson
2023-01-06 0:43 ` [PATCH v3 03/18] tcp: Combine two parts of passt tap send path together David Gibson
2023-01-06 0:43 ` [PATCH v3 04/18] tcp: Don't compute total bytes in a message until we need it David Gibson
2023-01-06 0:43 ` [PATCH v3 05/18] tcp: Improve interface to tcp_l2_buf_flush() David Gibson
2023-01-06 0:43 ` [PATCH v3 06/18] tcp: Combine two parts of pasta tap send path together David Gibson
2023-02-13 1:13 ` Stefano Brivio
2023-01-06 0:43 ` [PATCH v3 07/18] tap, tcp: Move tap send path to tap.c David Gibson
2023-01-06 0:43 ` [PATCH v3 08/18] util: Introduce hton*_constant() in place of #ifdefs David Gibson
2023-01-06 0:43 ` [PATCH v3 09/18] tcp, udp: Use named field initializers in iov_init functions David Gibson
2023-01-06 0:43 ` [PATCH v3 10/18] util: Parameterize ethernet header initializer macro David Gibson
2023-01-06 0:43 ` [PATCH v3 11/18] tcp: Remove redundant and incorrect initialization from *_iov_init() David Gibson
2023-01-06 0:43 ` [PATCH v3 12/18] tcp: Consolidate calculation of total frame size David Gibson
2023-01-06 0:43 ` [PATCH v3 13/18] tap: Add "tap headers" abstraction David Gibson
2023-01-06 0:43 ` [PATCH v3 14/18] tcp: Use abstracted tap header David Gibson
2023-01-06 0:43 ` [PATCH v3 15/18] tap: Use different io vector bases depending on tap type David Gibson
2023-01-06 0:43 ` [PATCH v3 16/18] udp: Use abstracted tap header David Gibson
2023-01-06 0:43 ` [PATCH v3 17/18] tap: Improve handling of partial frame sends David Gibson
2023-01-06 0:43 ` [PATCH v3 18/18] udp: Use tap_send_frames() David Gibson
2023-01-24 21:20 ` Stefano Brivio [this message]
2023-01-25 3:13 ` [PATCH v3 00/18] RFC: Unify and simplify tap send path David Gibson
2023-01-25 23:21 ` Stefano Brivio
2023-02-13 1:14 ` 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=20230124222043.281ef58c@elisabeth \
--to=sbrivio@redhat.com \
--cc=david@gibson.dropbear.id.au \
--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).