From: Simon Horman <horms@kernel.org>
To: carlos.bilbao@kernel.org
Cc: jv@jvosburgh.net, andrew+netdev@lunn.ch, davem@davemloft.net,
edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
sforshee@kernel.org, bilbao@vt.edu
Subject: Re: [PATCH] bonding: Switch periodic LACPDU state machine from counter to jiffies
Date: Wed, 16 Jul 2025 10:09:45 +0100 [thread overview]
Message-ID: <20250716090945.GL721198@horms.kernel.org> (raw)
In-Reply-To: <20250715205733.50911-1-carlos.bilbao@kernel.org>
On Tue, Jul 15, 2025 at 03:57:33PM -0500, carlos.bilbao@kernel.org wrote:
> From: Carlos Bilbao <carlos.bilbao@kernel.org>
>
> Replace the bonding periodic state machine for LACPDU transmission of
> function ad_periodic_machine() with a jiffies-based mechanism, which is
> more accurate and can help reduce drift under contention.
>
> Signed-off-by: Carlos Bilbao (DigitalOcean) <carlos.bilbao@kernel.org>
> ---
> drivers/net/bonding/bond_3ad.c | 79 +++++++++++++---------------------
> include/net/bond_3ad.h | 2 +-
> 2 files changed, 32 insertions(+), 49 deletions(-)
>
Hi Carlos,
Some minor feedback from my side.
> diff --git a/drivers/net/bonding/bond_3ad.c b/drivers/net/bonding/bond_3ad.c
...
> @@ -1471,21 +1451,24 @@ static void ad_periodic_machine(struct port *port, struct bond_params *bond_para
> "Periodic Machine: Port=%d, Last State=%d, Curr State=%d\n",
> port->actor_port_number, last_state,
> port->sm_periodic_state);
> +
> switch (port->sm_periodic_state) {
> - case AD_NO_PERIODIC:
> - port->sm_periodic_timer_counter = 0;
> - break;
> - case AD_FAST_PERIODIC:
> - /* decrement 1 tick we lost in the PERIODIC_TX cycle */
> - port->sm_periodic_timer_counter = __ad_timer_to_ticks(AD_PERIODIC_TIMER, (u16)(AD_FAST_PERIODIC_TIME))-1;
> - break;
> - case AD_SLOW_PERIODIC:
> - /* decrement 1 tick we lost in the PERIODIC_TX cycle */
> - port->sm_periodic_timer_counter = __ad_timer_to_ticks(AD_PERIODIC_TIMER, (u16)(AD_SLOW_PERIODIC_TIME))-1;
> - break;
> case AD_PERIODIC_TX:
> port->ntt = true;
> - break;
> + if (!(port->partner_oper.port_state &
> + LACP_STATE_LACP_TIMEOUT))
> + port->sm_periodic_state = AD_SLOW_PERIODIC;
> + else
> + port->sm_periodic_state = AD_FAST_PERIODIC;
> + fallthrough;
super-nit: maybe one more tab of indentation for the line above.
> + case AD_SLOW_PERIODIC:
> + case AD_FAST_PERIODIC:
> + if (port->sm_periodic_state == AD_SLOW_PERIODIC)
> + port->sm_periodic_next_jiffies = jiffies
> + + HZ * AD_SLOW_PERIODIC_TIME;
> + else /* AD_FAST_PERIODIC */
> + port->sm_periodic_next_jiffies = jiffies
> + + HZ * AD_FAST_PERIODIC_TIME;
Clang 20.1.8 complains that either a break; or fallthrough; should go here.
For consistency with the code above I'd suggest the latter.
> default:
> break;
> }
...
next prev parent reply other threads:[~2025-07-16 9:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-15 20:57 carlos.bilbao
2025-07-15 20:59 ` Carlos Bilbao
2025-07-16 15:30 ` Jay Vosburgh
2025-07-16 19:44 ` Carlos Bilbao
2025-07-16 23:33 ` Jay Vosburgh
2025-08-05 13:14 ` Hangbin Liu
2025-09-08 21:26 ` Carlos Bilbao
2025-09-09 3:25 ` Hangbin Liu
2025-07-16 9:09 ` Simon Horman [this message]
2025-07-16 19:45 ` Carlos Bilbao
2025-07-17 4:35 ` kernel test robot
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=20250716090945.GL721198@horms.kernel.org \
--to=horms@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=bilbao@vt.edu \
--cc=carlos.bilbao@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=jv@jvosburgh.net \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sforshee@kernel.org \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®