From: Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>
To: "Min Hu (Connor)" <humin29@huawei.com>, dev@dpdk.org
Cc: ferruh.yigit@intel.com
Subject: Re: [dpdk-dev] [PATCH] net/hns3: fix traffic management
Date: Thu, 1 Jul 2021 18:05:41 +0300 [thread overview]
Message-ID: <e5cbe6ca-9cab-cb8d-2554-733b50fb1fef@oktetlabs.ru> (raw)
In-Reply-To: <1624261125-22274-1-git-send-email-humin29@huawei.com>
On 6/21/21 10:38 AM, Min Hu (Connor) wrote:
> From: Huisong Li <lihuisong@huawei.com>
>
> In a multi-TC scenario, if the length of packets destined for different
> TCs is different, for example, 64B and 1500B packets destined for TC0 and
> TC1 respectively. There is a problem that the bandwidth of the TC to which
> large packets are sent is preempted by the TC to which small packets are
> sent on the Kunpeng 920 network engine. As a result, the TC bandwidth
> accuracy is inaccurate.
>
> To solve this problem, this patch made the following adjustments:
> 1/ During initialization, firmware reports the capability bit indicating
> whether the TM function is supported.
> 2/ The command word for configuring TC and port rate limiting is added,
> instead of reusing the existing command word. And firmware configured
> to the correct module.
> 3/ When the PF driver is loaded, firmware completes the default
> initialization of the TC and port.
>
> Fixes: c09c7847d892 ("net/hns3: support traffic management")
>
> Signed-off-by: Huisong Li <lihuisong@huawei.com>
> Signed-off-by: Min Hu (Connor) <humin29@huawei.com>
Applied, thanks.
prev parent reply other threads:[~2021-07-01 15:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-21 7:38 Min Hu (Connor)
2021-07-01 15:05 ` Andrew Rybchenko [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=e5cbe6ca-9cab-cb8d-2554-733b50fb1fef@oktetlabs.ru \
--to=andrew.rybchenko@oktetlabs.ru \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=humin29@huawei.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).