From: David Gibson <david@gibson.dropbear.id.au>
To: Stefano Brivio <sbrivio@redhat.com>
Cc: Laurent Vivier <lvivier@redhat.com>,
passt-dev@passt.top, Jon Maloy <jmaloy@redhat.com>
Subject: Re: [PATCH v8 17/19] conf, fwd: Allow switching to new rules received from pesto
Date: Wed, 6 May 2026 18:52:57 +1000 [thread overview]
Message-ID: <afsBaVhNfOiymYNJ@zatzit> (raw)
In-Reply-To: <20260506104955.51cdc602@elisabeth>
[-- Attachment #1: Type: text/plain, Size: 4869 bytes --]
On Wed, May 06, 2026 at 10:49:55AM +0200, Stefano Brivio wrote:
> On Wed, 6 May 2026 10:39:30 +0200
> Stefano Brivio <sbrivio@redhat.com> wrote:
>
> > On Wed, 6 May 2026 10:12:21 +0200
> > Laurent Vivier <lvivier@redhat.com> wrote:
> >
> > > On 5/6/26 01:47, Stefano Brivio wrote:
> > > > From: David Gibson <david@gibson.dropbear.id.au>
> > > >
> > > > We can now receive updates to the forwarding rules from the pesto client
> > > > and store them in a "pending" copy of the forwarding tables. Implement
> > > > switching to using the new rules.
> > > >
> > > > The logic is in a new fwd_listen_switch(). For now this closes all
> > > > listening sockets related to the old tables, swaps the active and pending
> > > > tables, then listens based on the new tables. In future we look to improve
> > > > this so that we don't temporarily stop listening on ports that both the
> > > > old and new tables specify.
> > > >
> > > > Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
> > > > [sbrivio: In fwd_listen_switch(), use the destination size as argument
> > > > to memcpy(), instead of sizeof(tmp), as suggested by Laurent]
> > > > Signed-off-by: Stefano Brivio <sbrivio@redhat.com>
> > > > ---
> > > > conf.c | 5 ++---
> > > > fwd.c | 34 ++++++++++++++++++++++++++++++++++
> > > > fwd.h | 1 +
> > > > 3 files changed, 37 insertions(+), 3 deletions(-)
> > > >
> > > > diff --git a/conf.c b/conf.c
> > > > index 76344da..3f48793 100644
> > > > --- a/conf.c
> > > > +++ b/conf.c
> > > > @@ -2160,15 +2160,14 @@ void conf_handler(struct ctx *c, uint32_t events)
> > > > fwd_rules_dump(info, fwd->rules, fwd->count,
> > > > " ", "");
> > > > }
> > > > +
> > > > + fwd_listen_switch(c);
> > > > }
> > > >
> > > > if (events & EPOLLHUP) {
> > > > debug("Configuration client hangup");
> > > > - goto close;
> > > > }
> > > >
> > > > - return;
> > > > -
> > > > close:
> > > > conf_close(c);
> > > >
> > > > diff --git a/fwd.c b/fwd.c
> > > > index d93d2e5..0697435 100644
> > > > --- a/fwd.c
> > > > +++ b/fwd.c
> > > > @@ -534,6 +534,40 @@ int fwd_listen_init(const struct ctx *c)
> > > > return 0;
> > > > }
> > > >
> > > > +/**
> > > > + * fwd_listen_switch() - Switch from current to pending rules table
> > > > + * @c: Execution context
> > > > + */
> > > > +void fwd_listen_switch(struct ctx *c)
> > > > +{
> > > > + struct fwd_table *tmp[PIF_NUM_TYPES];
> > > > + unsigned i;
> > > > +
> > > > + /* Stop listening on the old tables */
> > > > + for (i = 0; i < PIF_NUM_TYPES; i++) {
> > > > + struct fwd_table *fwd = c->fwd[i];
> > > > +
> > > > + if (!fwd)
> > > > + continue;
> > > > +
> > > > + debug("Flushing %u old %s rules", fwd->count, pif_name(i));
> > > > + fwd_listen_close(fwd);
> > > > + fwd->count = fwd->sock_count = 0;
> > > > + }
> > > > +
> > > > + /* Swap active and pending tables */
> > > > + static_assert(sizeof(tmp) == sizeof(c->fwd) &&
> > > > + sizeof(tmp) == sizeof(c->fwd_pending),
> > > > + "Temporary has wrong size");
> > >
> > > At this point:
> > >
> > > c->fwd[PIF_HOST] = &fwd_in;
> > > c->fwd[PIF_SPLICE] = &fwd_out;
> > >
> > > c->fwd_pending[PIF_HOST] = &fwd_in_pending;
> > > c->fwd_pending[PIF_SPLICE] = &fwd_out_pending;
> > >
> > > > + memcpy(&tmp, (void *)c->fwd, sizeof(tmp));
> > > > + memcpy((void *)c->fwd, (void *)c->fwd_pending, sizeof(c->fwd));
> > > > + memcpy((void *)c->fwd_pending, &tmp, sizeof(c->fwd_pending));
> > >
> > > At this point:
> > >
> > > c->fwd[PIF_HOST] = &fwd_in_pending;
> > > c->fwd[PIF_SPLICE] = &fwd_out_pending;
> > >
> > > c->fwd_pending[PIF_HOST] = &fwd_in;
> > > c->fwd_pending[PIF_SPLICE] = &fwd_out;
> >
> > Yeah, makes sense, I can change that in v9.
> >
> > > Perhaps it should be noted somewhere to avoid confusion in the future?
> >
> > What do you think should be noted exactly, and where? Can you show a
> > practical example of the change you're proposing?
>
> ...I'm leaving like it is in v9 to make sure I'm not misinterpreting
> you, and also because the current (v8) version is obviously correct and
> I also tested it fairly heavily by now.
>
> I'd suggest optimising this (and commenting as needed) in a separate
> patch later.
As noted in another branch of this thread, I think all it really needs
is renaming the globals that c->fwd and c->fwd_pending point to. They
should just be fwd_in_[12] (or an array of 2 tables), instead of
implying a semantic difference between the plain and "pending" copies.
--
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-05-06 8:53 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-05 23:47 [PATCH v8 00/19] Dynamic configuration update implementation Stefano Brivio
2026-05-05 23:47 ` [PATCH v8 01/19] conf, fwd: Stricter rule checking in fwd_rule_add() Stefano Brivio
2026-05-05 23:47 ` [PATCH v8 02/19] fwd_rule: Move ephemeral port probing to fwd_rule.c Stefano Brivio
2026-05-05 23:47 ` [PATCH v8 03/19] fwd, conf: Move rule parsing code to fwd_rule.[ch] Stefano Brivio
2026-05-05 23:47 ` [PATCH v8 04/19] fwd_rule: Move conflict checking back within fwd_rule_add() Stefano Brivio
2026-05-05 23:47 ` [PATCH v8 05/19] fwd: Generalise fwd_rules_info() Stefano Brivio
2026-05-05 23:47 ` [PATCH v8 06/19] pif: Limit pif names to 128 bytes Stefano Brivio
2026-05-05 23:47 ` [PATCH v8 07/19] fwd_rule: Fix some format specifiers Stefano Brivio
2026-05-05 23:47 ` [PATCH v8 08/19] pesto: Introduce stub configuration tool Stefano Brivio
2026-05-05 23:47 ` [PATCH v8 09/19] pesto, log: Share log.h (but not log.c) with pesto tool Stefano Brivio
2026-05-05 23:47 ` [PATCH v8 10/19] pesto, conf: Have pesto connect to passt and check versions Stefano Brivio
2026-05-06 5:38 ` David Gibson
2026-05-06 7:06 ` Laurent Vivier
2026-05-06 7:41 ` David Gibson
2026-05-06 7:55 ` Stefano Brivio
2026-05-06 8:21 ` David Gibson
2026-05-06 8:30 ` Stefano Brivio
2026-05-05 23:47 ` [PATCH v8 11/19] pesto: Expose list of pifs to pesto and display them Stefano Brivio
2026-05-05 23:47 ` [PATCH v8 12/19] ip: Prepare ip.[ch] for sharing with pesto tool Stefano Brivio
2026-05-05 23:47 ` [PATCH v8 13/19] inany: Prepare inany.[ch] " Stefano Brivio
2026-05-05 23:47 ` [PATCH v8 14/19] pesto: Read current ruleset from passt/pasta and optionally display it Stefano Brivio
2026-05-05 23:47 ` [PATCH v8 15/19] pesto: Parse and add new rules from command line Stefano Brivio
2026-05-06 7:13 ` Laurent Vivier
2026-05-06 9:15 ` Stefano Brivio
2026-05-05 23:47 ` [PATCH v8 16/19] pesto, conf: Send updated rules from pesto back to passt/pasta Stefano Brivio
2026-05-05 23:47 ` [PATCH v8 17/19] conf, fwd: Allow switching to new rules received from pesto Stefano Brivio
2026-05-06 7:15 ` Laurent Vivier
2026-05-06 8:12 ` Laurent Vivier
2026-05-06 8:23 ` David Gibson
2026-05-06 8:39 ` Stefano Brivio
2026-05-06 8:49 ` Stefano Brivio
2026-05-06 8:52 ` David Gibson [this message]
2026-05-06 9:11 ` Laurent Vivier
2026-05-06 12:11 ` Stefano Brivio
2026-05-05 23:47 ` [PATCH v8 18/19] fwd_rule: Fix static checkers warnings in fwd_rule_add() Stefano Brivio
2026-05-06 7:18 ` Laurent Vivier
2026-05-05 23:47 ` [PATCH v8 19/19] pesto, conf, fwd_rule: Add options and modes to add, delete, clear rules Stefano Brivio
2026-05-06 6:45 ` David Gibson
2026-05-06 8:22 ` Stefano Brivio
2026-05-06 8:48 ` David Gibson
2026-05-06 8:56 ` Stefano Brivio
2026-05-06 9:22 ` David Gibson
2026-05-06 12:52 ` Stefano Brivio
2026-05-06 6:53 ` [PATCH v8 00/19] Dynamic configuration update implementation 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=afsBaVhNfOiymYNJ@zatzit \
--to=david@gibson.dropbear.id.au \
--cc=jmaloy@redhat.com \
--cc=lvivier@redhat.com \
--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).