From: Slava Ovsiienko <viacheslavo@nvidia.com>
To: Martin Havlik <xhavli56@stud.fit.vutbr.cz>,
Xiaoyun Li <xiaoyun.li@intel.com>,
Ferruh Yigit <ferruh.yigit@intel.com>,
Andrew Rybchenko <arybchenko@solarflare.com>,
Ajit Khaparde <ajit.khaparde@broadcom.com>,
Haiyue Wang <haiyue.wang@intel.com>, Ori Kam <orika@nvidia.com>,
Haifei Luo <haifeil@nvidia.com>,
Andrey Vesnovaty <andreyv@nvidia.com>,
Bing Zhao <bingz@nvidia.com>,
"Jiawei(Jonny) Wang" <jiaweiw@nvidia.com>,
Gregory Etelson <getelson@nvidia.com>, Li Zhang <lizh@nvidia.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>, Jan Viktorin <viktorin@cesnet.cz>
Subject: RE: [PATCH 4/4] doc: note that testpmd on mlx5 has dedicated queues problem
Date: Mon, 6 Mar 2023 15:21:41 +0000 [thread overview]
Message-ID: <DM6PR12MB3753F5A2B6F55EE9C6988BBADFB69@DM6PR12MB3753.namprd12.prod.outlook.com> (raw)
In-Reply-To: <20210721155918.188867-5-xhavli56@stud.fit.vutbr.cz>
Hi, Martin
Is this issue resolved by: http://git.dpdk.org/dpdk/commit/?id=f66323717e ?
Should we archive the patch?
With best regards,
Slava
> -----Original Message-----
> From: Martin Havlik <xhavli56@stud.fit.vutbr.cz>
> Sent: среда, 21 июля 2021 г. 18:59
> To: xhavli56@stud.fit.vutbr.cz; Xiaoyun Li <xiaoyun.li@intel.com>; Ferruh Yigit
> <ferruh.yigit@intel.com>; Andrew Rybchenko <arybchenko@solarflare.com>;
> Ajit Khaparde <ajit.khaparde@broadcom.com>; Haiyue Wang
> <haiyue.wang@intel.com>; Ori Kam <orika@nvidia.com>; Haifei Luo
> <haifeil@nvidia.com>; Slava Ovsiienko <viacheslavo@nvidia.com>; Andrey
> Vesnovaty <andreyv@nvidia.com>; Bing Zhao <bingz@nvidia.com>;
> Jiawei(Jonny) Wang <jiaweiw@nvidia.com>; Gregory Etelson
> <getelson@nvidia.com>; Li Zhang <lizh@nvidia.com>
> Cc: dev@dpdk.org; Jan Viktorin <viktorin@cesnet.cz>
> Subject: [PATCH 4/4] doc: note that testpmd on mlx5 has dedicated queues
> problem
>
> In bonding mode 4 (8023ad), dedicated queues are not working on mlx5 NICs.
>
> Signed-off-by: Martin Havlik <xhavli56@stud.fit.vutbr.cz>
> ---
> doc/guides/testpmd_app_ug/testpmd_funcs.rst | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/doc/guides/testpmd_app_ug/testpmd_funcs.rst
> b/doc/guides/testpmd_app_ug/testpmd_funcs.rst
> index 2c43719ad3..8a6edc2bad 100644
> --- a/doc/guides/testpmd_app_ug/testpmd_funcs.rst
> +++ b/doc/guides/testpmd_app_ug/testpmd_funcs.rst
> @@ -2603,6 +2603,9 @@ when in mode 4 (link-aggregation-802.3ad)::
>
> testpmd> set bonding lacp dedicated_queues (port_id) (enable|disable)
>
> +.. note::
> + Dedicated queues `do not currently work
> + <https://bugs.dpdk.org/show_bug.cgi?id=759>`__ on mlx5 NICs.
>
> set bonding agg_mode
> ~~~~~~~~~~~~~~~~~~~~
> --
> 2.27.0
next prev parent reply other threads:[~2023-03-06 15:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-21 15:59 [dpdk-dev] " Martin Havlik
2023-03-06 15:21 ` Slava Ovsiienko [this message]
2023-03-07 9:00 ` Havlík Martin
2023-03-07 9:37 ` Jan Viktorin
2023-03-07 10:26 ` Mário Kuka
2023-03-07 10:29 ` Slava Ovsiienko
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=DM6PR12MB3753F5A2B6F55EE9C6988BBADFB69@DM6PR12MB3753.namprd12.prod.outlook.com \
--to=viacheslavo@nvidia.com \
--cc=ajit.khaparde@broadcom.com \
--cc=andreyv@nvidia.com \
--cc=arybchenko@solarflare.com \
--cc=bingz@nvidia.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=getelson@nvidia.com \
--cc=haifeil@nvidia.com \
--cc=haiyue.wang@intel.com \
--cc=jiaweiw@nvidia.com \
--cc=lizh@nvidia.com \
--cc=orika@nvidia.com \
--cc=viktorin@cesnet.cz \
--cc=xhavli56@stud.fit.vutbr.cz \
--cc=xiaoyun.li@intel.com \
/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).