From: Stefano Brivio <sbrivio@redhat.com>
To: David Gibson <david@gibson.dropbear.id.au>
Cc: passt-dev@passt.top
Subject: Re: [PATCH v2 0/4] Even more flow table preliminaries
Date: Fri, 14 Jun 2024 13:14:27 +0200 [thread overview]
Message-ID: <20240614131427.494638d0@elisabeth> (raw)
In-Reply-To: <20240614015108.2761502-1-david@gibson.dropbear.id.au>
On Fri, 14 Jun 2024 11:51:04 +1000
David Gibson <david@gibson.dropbear.id.au> wrote:
> I hoped that the last batch was the last, but I was wrong. Working on
> UDP flow has shown up a few more things that make sense to do before
> taking the leap into full flow table implementation. Here's what I
> have so far, though there could be even more.
>
> Changes since v1:
> * Assorted minor style and comment changes based on Stefano's review.
>
> David Gibson (4):
> util: Split construction of bind socket address from the rest of
> sock_l4()
> udp: Fold checking of splice flag into udp_mmh_splice_port()
> udp: Rework how we divide queued datagrams between sending methods
> udp: Move management of udp[46]_localname into udp_splice_send()
>
> udp.c | 176 +++++++++++++++++++++++++++++++++------------------------
> util.c | 123 +++++++++++++++++++++++-----------------
> 2 files changed, 171 insertions(+), 128 deletions(-)
Applied.
--
Stefano
prev parent reply other threads:[~2024-06-14 11:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-14 1:51 [PATCH v2 0/4] Even more flow table preliminaries David Gibson
2024-06-14 1:51 ` [PATCH v2 1/4] util: Split construction of bind socket address from the rest of sock_l4() David Gibson
2024-06-14 1:51 ` [PATCH v2 2/4] udp: Fold checking of splice flag into udp_mmh_splice_port() David Gibson
2024-06-14 1:51 ` [PATCH v2 3/4] udp: Rework how we divide queued datagrams between sending methods David Gibson
2024-06-14 1:51 ` [PATCH v2 4/4] udp: Move management of udp[46]_localname into udp_splice_send() David Gibson
2024-06-14 11:14 ` 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=20240614131427.494638d0@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).