From: "jiangheng (G)" <jiangheng14@huawei.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: "beilei.xing@intel.com" <beilei.xing@intel.com>,
"users@dpdk.org" <users@dpdk.org>,
"Fanbin(Kira,2012 Blue Lab.)" <fanbin12@huawei.com>
Subject: 答复: Whether the creatation of flow rules of i40e NIC support tcp port mask
Date: Wed, 18 Oct 2023 01:48:05 +0000 [thread overview]
Message-ID: <da46dd4def5e4d8c89d4a56ff1824c56@huawei.com> (raw)
In-Reply-To: <20231017085225.1b35dee7@hermes.local>
Hi Stephen:
I am trying to shorten mask, but flow rules s not working.in i40e NIC.
Please see i40e pmd code:
https://github.com/DPDK/dpdk/blob/v22.11/drivers/net/i40e/i40e_flow.c#L2036
It only determines that the mask is UINT16_MAX, and setting mask to other value seems no difference.
-----邮件原件-----
发件人: Stephen Hemminger <stephen@networkplumber.org>
发送时间: 2023年10月17日 23:52
收件人: jiangheng (G) <jiangheng14@huawei.com>
抄送: beilei.xing@intel.com; users@dpdk.org; Fanbin(Kira,2012 Blue Lab.) <fanbin12@huawei.com>
主题: Re: Whether the creatation of flow rules of i40e NIC support tcp port mask
On Tue, 17 Oct 2023 08:52:22 +0000
"jiangheng (G)" <jiangheng14@huawei.com> wrote:
> Hi beilei，
>
> I would like to create flows using tcp port mask, but it seems only mask 0xffff or 0x0 work, Does flow rlue can be created using other mask?
>
> I40e dirver was using now.
Why not create multiple rules each pointing at same action?
Or is mask so wide that you run out of rte_flow slots.
next prev parent reply other threads:[~2023-10-18 1:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-17 8:52 jiangheng (G)
2023-10-17 15:52 ` Stephen Hemminger
2023-10-18 1:48 ` jiangheng (G) [this message]
2023-10-18 1:54 ` Xing, Beilei
2023-10-18 2:19 ` 答复: " jiangheng (G)
2023-10-18 4:09 ` Xing, Beilei
2023-10-18 7:21 ` Lukáš Šišmiš
2023-10-18 11:16 ` 答复: " jiangheng (G)
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=da46dd4def5e4d8c89d4a56ff1824c56@huawei.com \
--to=jiangheng14@huawei.com \
--cc=beilei.xing@intel.com \
--cc=fanbin12@huawei.com \
--cc=stephen@networkplumber.org \
--cc=users@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).