From: Stephen Hemminger <stephen@networkplumber.org>
To: Jie Hai <haijie1@huawei.com>
Cc: <dev@dpdk.org>, <thomas@monjalon.net>, <ferruh.yigit@amd.com>,
Chengwen Feng <fengchengwen@huawei.com>,
"Wei Hu (Xavier)" <xavier.huwei@huawei.com>,
Chunsong Feng <fengchunsong@huawei.com>,
Huisong Li <lihuisong@huawei.com>,
"Min Hu (Connor)" <humin29@huawei.com>, <huangdengdui@huawei.com>
Subject: Re: [PATCH 2/2] net/hns3: fix cannot fully use hardware flow director table
Date: Thu, 7 Nov 2024 08:21:39 -0800 [thread overview]
Message-ID: <20241107082139.35728fff@hermes.local> (raw)
In-Reply-To: <20241107115645.22617-3-haijie1@huawei.com>
On Thu, 7 Nov 2024 19:56:45 +0800
Jie Hai <haijie1@huawei.com> wrote:
> From: Dengdui Huang <huangdengdui@huawei.com>
>
> The hns3 driver checks whether the flow rule is repeatedly inserted based
> on rte_hash. Currently, the rte_hash extendable bucket table feature is not
> enabled. When there are many hash conflicts, the hash table space cannot be
> fully used. So the flow rule maybe cannot be inserted even if the hardware
> flow director table there are still free. This patch fix it by enabling the
> rte_hash extensible bucket table feature.
>
> Fixes: fcba820d9b9e ("net/hns3: support flow director")
> Cc: stable@dpdk.org
>
> Signed-off-by: Dengdui Huang <huangdengdui@huawei.com>
> Signed-off-by: Jie Hai <haijie1@huawei.com>
> ---
Acked-by: Stephen Hemminger <stephen@networkplumber.org>
next prev parent reply other threads:[~2024-11-07 16:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-07 11:56 [PATCH 0/2] net/hns3: bugfix for hns3 Jie Hai
2024-11-07 11:56 ` [PATCH 1/2] net/hns3: fix error code for repeatedly create counter Jie Hai
2024-11-07 16:21 ` Stephen Hemminger
2024-11-07 11:56 ` [PATCH 2/2] net/hns3: fix cannot fully use hardware flow director table Jie Hai
2024-11-07 16:21 ` Stephen Hemminger [this message]
2024-11-10 22:52 ` [PATCH 0/2] net/hns3: bugfix for hns3 Ferruh Yigit
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=20241107082139.35728fff@hermes.local \
--to=stephen@networkplumber.org \
--cc=dev@dpdk.org \
--cc=fengchengwen@huawei.com \
--cc=fengchunsong@huawei.com \
--cc=ferruh.yigit@amd.com \
--cc=haijie1@huawei.com \
--cc=huangdengdui@huawei.com \
--cc=humin29@huawei.com \
--cc=lihuisong@huawei.com \
--cc=thomas@monjalon.net \
--cc=xavier.huwei@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.