From: Thomas Monjalon <thomas@monjalon.net>
To: Arik Alexander <arik.alexander@catonetworks.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
Dima Babich <dima@catonetworks.com>,
Chas Williams <chas3@att.com>, Min Hu <humin29@huawei.com>,
Bruce Richardson <bruce.richardson@intel.com>,
Chengwen Feng <fengchengwen@huawei.com>,
Huisong Li <lihuisong@huawei.com>,
Stephen Hemminger <stephen@networkplumber.org>,
Ivan Malov <ivan.malov@oktetlabs.ru>
Subject: Re: DPDK LACP implemantation
Date: Thu, 18 Sep 2025 11:06:48 +0200 [thread overview]
Message-ID: <3392247.jE0xQCEvom@thomas> (raw)
In-Reply-To: <DB7PR03MB48906F6B09425E675420A8A6F217A@DB7PR03MB4890.eurprd03.prod.outlook.com>
Hello,
17/09/2025 16:07, Arik Alexander:
> At Cato Networks we are currently working on implementing LACP LAG (bonding device, mode 4) using the DPDK library.
> During our evaluation, we identified some shortcomings in the implementation — for example, the lack of support for short timeout and the absence of proper handling for partner key mismatches.
Thanks for reporting.
I'm adding relevant maintainers to this thread.
> These gaps, combined with the lack of complaints or upstream patches addressing them, raise concerns about the maturity and stability of the library.
> We would be grateful if you could clarify the following:
>
> *
> To what extent is the DPDK bonding/LACP code deployed in production enterprise environments?
> *
> Is it possible to share the names of companies or organizations that use it in production?
Sorry we don't know where bonding is deployed,
but you can check who contributed to it.
You are welcome to report the specific issues in bugs.dpdk.org
and/or send your improvements.
Thank you
prev parent reply other threads:[~2025-09-18 9:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-17 14:07 Arik Alexander
2025-09-18 9:06 ` Thomas Monjalon [this message]
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=3392247.jE0xQCEvom@thomas \
--to=thomas@monjalon.net \
--cc=arik.alexander@catonetworks.com \
--cc=bruce.richardson@intel.com \
--cc=chas3@att.com \
--cc=dev@dpdk.org \
--cc=dima@catonetworks.com \
--cc=fengchengwen@huawei.com \
--cc=humin29@huawei.com \
--cc=ivan.malov@oktetlabs.ru \
--cc=lihuisong@huawei.com \
--cc=stephen@networkplumber.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;
as well as URLs for NNTP newsgroup(s).