From: "Li, WeiyuanX" <weiyuanx.li@intel.com>
To: Ivan Malov <ivan.malov@oktetlabs.ru>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "stable@dpdk.org" <stable@dpdk.org>,
Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>,
Chas Williams <chas3@att.com>,
"Min Hu (Connor)" <humin29@huawei.com>,
Hari Kumar Vemula <hari.kumarx.vemula@intel.com>
Subject: meson test link bonding failed//RE: [PATCH] net/bonding: fix descriptor limit reporting
Date: Mon, 31 Oct 2022 09:04:42 +0000 [thread overview]
Message-ID: <CH3PR11MB7275D033FCCE0FA353042CD2E4379@CH3PR11MB7275.namprd11.prod.outlook.com> (raw)
Hi Ivan,
This patch is merged into dpdk22.11.0rc1 we execute meson test case link_bonding_autotest, link_bonding_rssconf_autotest and link_bonding_mode4_autotest test failed.
Could you please have a look at it, also submitted a Bugzilla ticket: https://bugs.dpdk.org/show_bug.cgi?id=1118
Regards,
Li, Weiyuan
> -----Original Message-----
> From: Ivan Malov <ivan.malov@oktetlabs.ru>
> Sent: Sunday, September 11, 2022 8:19 PM
> To: dev@dpdk.org
> Cc: stable@dpdk.org; Andrew Rybchenko
> <andrew.rybchenko@oktetlabs.ru>; Chas Williams <chas3@att.com>; Min
> Hu (Connor) <humin29@huawei.com>; Hari Kumar Vemula
> <hari.kumarx.vemula@intel.com>
> Subject: [PATCH] net/bonding: fix descriptor limit reporting
>
> Commit 5be3b40fea60 ("net/bonding: fix values of descriptor limits") breaks
> reporting of "nb_min" and "nb_align" values obtained from back-end
> devices' descriptor limits. This means that work done by
> eth_bond_slave_inherit_desc_lim_first() as well as
> eth_bond_slave_inherit_desc_lim_next() gets dismissed.
>
> Revert the offending commit and use proper workaround for the test case
> mentioned in the said commit.
>
> Meanwhile, the test case itself might be poorly constructed.
> It tries to run a bond with no back-end devices attached, but, according to [1]
> ("Requirements / Limitations"), at least one back-end device must be
> attached.
>
> [1] doc/guides/prog_guide/link_bonding_poll_mode_drv_lib.rst
>
> Fixes: 5be3b40fea60 ("net/bonding: fix values of descriptor limits")
> Cc: stable@dpdk.org
>
> Signed-off-by: Ivan Malov <ivan.malov@oktetlabs.ru>
> Reviewed-by: Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>
> ---
next reply other threads:[~2022-10-31 9:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-31 9:04 Li, WeiyuanX [this message]
2022-10-31 13:43 ` Ivan Malov
2022-11-02 3:23 ` Li, WeiyuanX
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=CH3PR11MB7275D033FCCE0FA353042CD2E4379@CH3PR11MB7275.namprd11.prod.outlook.com \
--to=weiyuanx.li@intel.com \
--cc=andrew.rybchenko@oktetlabs.ru \
--cc=chas3@att.com \
--cc=dev@dpdk.org \
--cc=hari.kumarx.vemula@intel.com \
--cc=humin29@huawei.com \
--cc=ivan.malov@oktetlabs.ru \
--cc=stable@dpdk.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).