From: Stefano Brivio <sbrivio@redhat.com>
To: David Gibson <david@gibson.dropbear.id.au>
Cc: passt-dev@passt.top
Subject: Re: [PATCH 0/5] RFC: Forwarding table data structure
Date: Sat, 13 Dec 2025 02:55:12 +0100 [thread overview]
Message-ID: <20251213025512.5240a38b@elisabeth> (raw)
In-Reply-To: <20251212071038.3943933-1-david@gibson.dropbear.id.au>
On Fri, 12 Dec 2025 18:10:33 +1100
David Gibson <david@gibson.dropbear.id.au> wrote:
> Here's some patches starting to create a data structure to store more
> flexible (and eventually dynamically updateable) forwarding
> configuration.
>
> So far this is just creating the data structures, not actually using
> them to drive the rest of the code, so it's not ready for merge (but
> the preliminaries in 1..2/5 could be merged if you like). Putting it
> out there for early review.
>
> David Gibson (5):
> tcp: Remove extra space from TCP_INFO debug messages (trivial)
> conf, fwd: Move initialisation of auto port scanning out of conf()
> conf, fwd: Keep a table of our port forwarding configuration
> conf: Accurately record ifname and address for outbound forwards
> conf, fwd: Record "auto" port forwards in forwarding table
Applied up to 2/5, review of the rest will come in a bit.
--
Stefano
prev parent reply other threads:[~2025-12-13 1:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-12 7:10 David Gibson
2025-12-12 7:10 ` [PATCH 1/5] tcp: Remove extra space from TCP_INFO debug messages (trivial) David Gibson
2025-12-12 7:10 ` [PATCH 2/5] conf, fwd: Move initialisation of auto port scanning out of conf() David Gibson
2025-12-12 7:10 ` [PATCH 3/5] conf, fwd: Keep a table of our port forwarding configuration David Gibson
2025-12-12 7:10 ` [PATCH 4/5] conf: Accurately record ifname and address for outbound forwards David Gibson
2025-12-12 7:10 ` [PATCH 5/5] conf, fwd: Record "auto" port forwards in forwarding table David Gibson
2025-12-13 1:55 ` 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=20251213025512.5240a38b@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).