mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Carlos Bilbao <carlos.bilbao.osdev@gmail.com>
To: Hangbin Liu <liuhangbin@gmail.com>, Carlos Bilbao <bilbao@vt.edu>
Cc: 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: Mon, 8 Sep 2025 16:26:12 -0500	[thread overview]
Message-ID: <49b975a6-25ad-4c11-a221-952b466d267e@gmail.com> (raw)
In-Reply-To: <aJIDoJ4Fp9AWbKWI@fedora>

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.

>
> [1] lacpd: https://github.com/liuhangbin/lacpd
>
> Thanks
> Hangbin


Thanks,

Carlos


  reply	other threads:[~2025-09-08 21:26 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 [this message]
2025-09-09  3:25       ` Hangbin Liu
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=49b975a6-25ad-4c11-a221-952b466d267e@gmail.com \
    --to=carlos.bilbao.osdev@gmail.com \
    --cc=andrew+netdev@lunn.ch \
    --cc=bilbao@vt.edu \
    --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=liuhangbin@gmail.com \
    --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®