From: David Gibson <david@gibson.dropbear.id.au>
To: Stefano Brivio <sbrivio@redhat.com>, passt-dev@passt.top
Cc: David Gibson <david@gibson.dropbear.id.au>
Subject: [PATCH 0/4] Even more flow table preliminaries
Date: Wed, 5 Jun 2024 11:38:59 +1000 [thread overview]
Message-ID: <20240605013903.3694452-1-david@gibson.dropbear.id.au> (raw)
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.
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 | 175 ++++++++++++++++++++++++++++++++-------------------------
util.c | 123 +++++++++++++++++++++++-----------------
2 files changed, 170 insertions(+), 128 deletions(-)
--
2.45.1
next reply other threads:[~2024-06-05 1:39 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-05 1:38 David Gibson [this message]
2024-06-05 1:39 ` [PATCH 1/4] util: Split construction of bind socket address from the rest of sock_l4() David Gibson
2024-06-13 15:06 ` Stefano Brivio
2024-06-14 0:47 ` David Gibson
2024-06-05 1:39 ` [PATCH 2/4] udp: Fold checking of splice flag into udp_mmh_splice_port() David Gibson
2024-06-13 15:06 ` Stefano Brivio
2024-06-14 0:50 ` David Gibson
2024-06-05 1:39 ` [PATCH 3/4] udp: Rework how we divide queued datagrams between sending methods David Gibson
2024-06-13 18:21 ` Stefano Brivio
2024-06-14 1:08 ` David Gibson
2024-06-05 1:39 ` [PATCH 4/4] udp: Move management of udp[46]_localname into udp_splice_send() 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=20240605013903.3694452-1-david@gibson.dropbear.id.au \
--to=david@gibson.dropbear.id.au \
--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).