From: Stefano Brivio <sbrivio@redhat.com>
To: Jon Maloy <jmaloy@redhat.com>
Cc: david@gibson.dropbear.id.au, passt-dev@passt.top
Subject: Re: [PATCH v6 02/13] ip: Introduce unified multi-address data structures
Date: Thu, 02 Apr 2026 22:33:56 +0200 (CEST) [thread overview]
Message-ID: <20260402223355.24528e0f@elisabeth> (raw)
In-Reply-To: <20260330235710.3b0570fe@elisabeth>
On Mon, 30 Mar 2026 23:57:10 +0200
Stefano Brivio <sbrivio@redhat.com> wrote:
> On Sat, 21 Mar 2026 20:43:22 -0400
> Jon Maloy <jmaloy@redhat.com> wrote:
>
> [...]
>
> > +/**
> > + * fwd_get_addr() - Get guest address entry matching criteria
> > + * @c: Execution context
> > + * @af: Address family (AF_INET, AF_INET6, or 0 for any)
> > + * @incl: Flags that must be present (any-match)
> > + * @excl: Flags that must not be present
> > + *
> > + * Return: first address entry matching criteria, or NULL
> > + */
> > +const struct guest_addr *fwd_get_addr(const struct ctx *c, sa_family_t af,
> > + uint8_t incl, uint8_t excl)
> > +{
> > + const struct guest_addr *a;
> > +
> > + for_each_addr(a, c, af) {
> > + if (incl && !(a->flags & incl))
> > + continue;
> > + if (a->flags & excl)
> > + continue;
>
> Slightly less generic, but maybe good enough for this purpose: you
> could admit a set of flags, or a negation of a flag (for example
> ~CONF_ADDR_USER), in a single argument.
>
> See how conn_flag_do() does that. Here it would be something like:
>
> if (flags & (flags - 1)) {
> if (a->flags & ~flag)
> continue;
> } else {
> if (!(a->flags & flag))
> continue;
> }
>
> ...it makes callers more readable in my opinion, for example:
>
> a = fwd_get_addr(c, AF_INET6, ~CONF_ADDR_LINKLOCAL);
>
> which makes it entirely clear you're selecting all addresses that are
> link-local, compared to:
>
> a = fwd_get_addr(c, AF_INET6, 0, CONF_ADDR_LINKLOCAL);
>
> which forces the reader to look up the prototype.
>
> But again it's less generic, you can't exclude multiple flags like
> that. Unless... you define a reserved bit which is always 0 in that
> uint8_t, so that if you pass it as 1, you can conclude a negated set of
> flags was passed.
...at least until I finally reached 9/13 where you pass both matching
and non-matching flags, and my trick doesn't work anymore. Oops, sorry.
--
Stefano
next prev parent reply other threads:[~2026-04-02 20:34 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-22 0:43 [PATCH v6 00/13] Introduce multiple addresses and late binding Jon Maloy
2026-03-22 0:43 ` [PATCH v6 01/13] conf: use a single buffer for print formatting in conf_print() Jon Maloy
2026-03-23 23:26 ` David Gibson
2026-03-30 21:57 ` Stefano Brivio
2026-03-22 0:43 ` [PATCH v6 02/13] ip: Introduce unified multi-address data structures Jon Maloy
2026-03-24 3:31 ` David Gibson
2026-03-30 21:57 ` Stefano Brivio
2026-04-02 20:33 ` Stefano Brivio [this message]
2026-03-22 0:43 ` [PATCH v6 03/13] fwd: Unify guest accessibility checks with unified address array Jon Maloy
2026-03-24 3:45 ` David Gibson
2026-03-30 21:57 ` Stefano Brivio
2026-03-22 0:43 ` [PATCH v6 04/13] arp: Check all configured addresses in ARP filtering Jon Maloy
2026-03-30 21:57 ` Stefano Brivio
2026-03-22 0:43 ` [PATCH v6 05/13] conf: Allow multiple -a/--address options per address family Jon Maloy
2026-03-24 5:29 ` David Gibson
2026-03-30 21:57 ` Stefano Brivio
2026-03-22 0:43 ` [PATCH v6 06/13] netlink, conf: Read all addresses from template interface at startup Jon Maloy
2026-03-24 5:36 ` David Gibson
2026-03-30 21:57 ` Stefano Brivio
2026-03-22 0:43 ` [PATCH v6 07/13] ip: refactor function pasta_ns_conf() Jon Maloy
2026-03-24 5:49 ` David Gibson
2026-03-22 0:43 ` [PATCH v6 08/13] ip: Track observed guest IPv4 addresses in unified address array Jon Maloy
2026-03-25 0:48 ` David Gibson
2026-04-02 20:34 ` Stefano Brivio
2026-03-22 0:43 ` [PATCH v6 09/13] ip: Track observed guest IPv6 " Jon Maloy
2026-03-25 1:08 ` David Gibson
2026-04-02 20:34 ` Stefano Brivio
2026-03-22 0:43 ` [PATCH v6 10/13] migrate: Update protocol to v3 for multi-address support Jon Maloy
2026-03-25 1:22 ` David Gibson
2026-04-02 21:55 ` Stefano Brivio
2026-03-22 0:43 ` [PATCH v6 11/13] dhcp: Select address for DHCP distribution Jon Maloy
2026-03-25 1:26 ` David Gibson
2026-04-02 21:55 ` Stefano Brivio
2026-03-22 0:43 ` [PATCH v6 12/13] dhcpv6: Select addresses for DHCPv6 distribution Jon Maloy
2026-03-25 1:40 ` David Gibson
2026-04-02 21:55 ` Stefano Brivio
2026-03-22 0:43 ` [PATCH v6 13/13] ndp: Support advertising multiple prefixes in Router Advertisements Jon Maloy
2026-03-25 1:46 ` David Gibson
2026-04-02 21:55 ` 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=20260402223355.24528e0f@elisabeth \
--to=sbrivio@redhat.com \
--cc=david@gibson.dropbear.id.au \
--cc=jmaloy@redhat.com \
--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).