From: David Gibson <david@gibson.dropbear.id.au>
To: Stefano Brivio <sbrivio@redhat.com>
Cc: passt-dev@passt.top
Subject: Re: [PATCH v3 02/14] conf, fwd: Keep a table of our port forwarding configuration
Date: Wed, 14 Jan 2026 10:53:01 +1100 [thread overview]
Message-ID: <aWba3eh2T2jZOVfX@zatzit> (raw)
In-Reply-To: <20260113231326.6bc2ecf2@elisabeth>
[-- Attachment #1: Type: text/plain, Size: 2052 bytes --]
On Tue, Jan 13, 2026 at 11:13:26PM +0100, Stefano Brivio wrote:
> On Tue, 13 Jan 2026 16:12:02 +1100
> David Gibson <david@gibson.dropbear.id.au> wrote:
>
> > On Tue, Jan 13, 2026 at 12:26:10AM +0100, Stefano Brivio wrote:
> > >
> > > On Thu, 8 Jan 2026 13:29:36 +1100
> > > David Gibson <david@gibson.dropbear.id.au> wrote:
> > >
> > > > +/**
> > > > + * fwd_rules_print() - Print forwarding rules for debugging
> > > > + * @fwd: Table to print
> > > > + */
> > > > +void fwd_rules_print(const struct fwd_ports *fwd)
> > > > +{
> > > > + unsigned i;
> > > > +
> > > > + for (i = 0; i < fwd->count; i++) {
> > > > + const struct fwd_rule *rule = &fwd->rules[i];
> > > > + const char *weak = rule->flags & FWD_WEAK ? " WEAK" : "";
> > >
> > > Should we print " might fail" or " can fail" instead of " WEAK"? This
> > > is for users.
> >
> > Good point. THough I'm not sure "might fail" or "can fail" is
> > terribly clear in context either. I've gone with " (best effort)" for
> > now.
>
> Or maybe " (if available)"?
I feel like that's also kind of vague. Available where, exactly?
> I always find "best effort" a bit ambiguous
> because, well, it's a pretty good effort, being it's the best one, but
> it actually means we'll just give it a quick try,
I'm thinking of it as "best effort" for the rule as a whole: we
attempt it for every component port.
> once.
That's no longer true after 7/14: we'll call fwd_listen_sync() every
second from fwd_scan_ports_timer(). That's intended for the FWD_SCAN
rules, but it also means we'll re-attempt listens for any FWD_WEAK
ports we previously failed on.
> No strong preference though, "best effort" is rather idiomatic anyway.
I'll keep it as-is for now, but I'm open to different wordings if a
clearly better one occurs to one of us.
--
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:[~2026-01-14 0:42 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-08 2:29 [PATCH v3 00/14] Introduce forwarding table David Gibson
2026-01-08 2:29 ` [PATCH v3 01/14] inany: Extend inany_ntop() to treat NULL as a fully unspecified address David Gibson
2026-01-08 13:16 ` Laurent Vivier
2026-01-08 2:29 ` [PATCH v3 02/14] conf, fwd: Keep a table of our port forwarding configuration David Gibson
2026-01-12 23:26 ` Stefano Brivio
2026-01-13 5:12 ` David Gibson
2026-01-13 22:13 ` Stefano Brivio
2026-01-13 23:53 ` David Gibson [this message]
2026-01-08 2:29 ` [PATCH v3 03/14] conf: Accurately record ifname and address for outbound forwards David Gibson
2026-01-08 2:29 ` [PATCH v3 04/14] conf, fwd: Record "auto" port forwards in forwarding table David Gibson
2026-01-12 23:26 ` Stefano Brivio
2026-01-13 5:14 ` David Gibson
2026-01-08 2:29 ` [PATCH v3 05/14] fwd: Make space to store listening sockets in forward table David Gibson
2026-01-12 23:26 ` Stefano Brivio
2026-01-13 5:28 ` David Gibson
2026-01-13 22:13 ` Stefano Brivio
2026-01-13 23:57 ` David Gibson
2026-01-08 2:29 ` [PATCH v3 06/14] ip: Add ipproto_name() function David Gibson
2026-01-08 13:22 ` Laurent Vivier
2026-01-08 23:12 ` David Gibson
2026-01-08 2:29 ` [PATCH v3 07/14] fwd, tcp, udp: Set up listening sockets based on forward table David Gibson
2026-01-12 23:26 ` Stefano Brivio
2026-01-13 5:38 ` David Gibson
2026-01-13 22:13 ` Stefano Brivio
2026-01-13 23:59 ` David Gibson
2026-01-08 2:29 ` [PATCH v3 08/14] tcp, udp: Remove old auto-forwarding socket arrays David Gibson
2026-01-08 2:29 ` [PATCH v3 09/14] conf, fwd: Check forwarding table for conflicting rules David Gibson
2026-01-12 23:26 ` Stefano Brivio
2026-01-13 5:41 ` David Gibson
2026-01-08 2:29 ` [PATCH v3 10/14] fwd: Generate auto-forward exclusions from socket fd tables David Gibson
2026-01-08 2:29 ` [PATCH v3 11/14] flow, fwd: Consult rules table when forwarding a new flow from socket David Gibson
2026-01-13 22:12 ` Stefano Brivio
2026-01-14 0:09 ` David Gibson
2026-01-08 2:29 ` [PATCH v3 12/14] fwd: Remap ports based directly on forwarding rule David Gibson
2026-01-13 22:12 ` Stefano Brivio
2026-01-14 0:24 ` David Gibson
2026-01-08 2:29 ` [PATCH v3 13/14] fwd, tcp, udp: Add forwarding rule to listening socket epoll references David Gibson
2026-01-13 22:12 ` Stefano Brivio
2026-01-14 0:37 ` David Gibson
2026-01-08 2:29 ` [PATCH v3 14/14] flow, fwd: Optimise forwarding rule lookup using epoll ref when possible David Gibson
2026-01-13 22:13 ` Stefano Brivio
2026-01-14 1:06 ` 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=aWba3eh2T2jZOVfX@zatzit \
--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).