From: Hangbin Liu <liuhangbin@gmail.com>
To: Carlos Bilbao <carlos.bilbao.osdev@gmail.com>
Cc: Carlos Bilbao <bilbao@vt.edu>,
carlos.bilbao@kernel.org, jv@jvosburgh.net,
andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, horms@kernel.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
sforshee@kernel.org
Subject: Re: [PATCH] bonding: Switch periodic LACPDU state machine from counter to jiffies
Date: Tue, 9 Sep 2025 03:25:58 +0000 [thread overview]
Message-ID: <aL-eRu6eTHb3eB3A@fedora> (raw)
In-Reply-To: <49b975a6-25ad-4c11-a221-952b466d267e@gmail.com>
On Mon, Sep 08, 2025 at 04:26:12PM -0500, Carlos Bilbao wrote:
> Hey Hangbin,
>
> On 8/5/25 08:14, Hangbin Liu wrote:
> > On Tue, Jul 15, 2025 at 03:59:39PM -0500, Carlos Bilbao wrote:
> > > FYI, I was able to test this locally but couldn’t find any kselftests to
> > > stress the bonding state machine. If anyone knows of additional ways to
> > > test it, I’d be happy to run them.
> > Hi Carlos,
> >
> > I have wrote a tool[1] to do lacp simulation and state injection. Feel free to
> > try it and open feature requests.
>
>
> Very cool, thanks for the effort! If you’d like to run my bonding patch
> through your new tool, I’ll be happy to add your Tested-by tag.
What kind of tests do you want to run?
Hangbin
>
> >
> > [1] lacpd: https://github.com/liuhangbin/lacpd
> >
> > Thanks
> > Hangbin
>
>
> Thanks,
>
> Carlos
>
next prev parent reply other threads:[~2025-09-09 3:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-15 20:57 [PATCH] bonding: Switch periodic LACPDU state machine from counter to jiffies 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 [this message]
2025-07-16 9:09 ` Simon Horman
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=aL-eRu6eTHb3eB3A@fedora \
--to=liuhangbin@gmail.com \
--cc=andrew+netdev@lunn.ch \
--cc=bilbao@vt.edu \
--cc=carlos.bilbao.osdev@gmail.com \
--cc=carlos.bilbao@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.