From: Junlong Wang <wang.junlong1@zte.com.cn>
To: ivan.malov@arknetworks.am, stephen@networkplumber.org
Cc: chen.bingbin@zte.com.cn, dev@dpdk.org
Subject: [v4,2/2] net/zxdh: add support flow director ops
Date: Tue, 12 Aug 2025 18:47:03 +0800 [thread overview]
Message-ID: <20250812104703.2111951-1-wang.junlong1@zte.com.cn> (raw)
In-Reply-To: <20250808071048.1906724-3-wang.junlong1@zte.com.cn>
[-- Attachment #1.1.1: Type: text/plain, Size: 1291 bytes --]
> > > Wait a minute.. does this mean that if the user passes, say, ETH / IPV4 / UDP
> > > pattern and the 'spec' and 'mask' of ETH are both 'null', the actual key/mask
> > > values in the HW rule will be, say, for the EtherType, '0000' and 'ffff'?
> > > Is this correct? And which part of DPDK interface envisages that?
> >
> > > Again, may be it's just my misunderstanding.
> >
> > Sorry, I misunderstood and caused you inconvenience.
> > If the user does not set 'spec' and 'mask', we will set 'spec' '0000' and mask 'ffff' write fd table to HW,
> > not set by DPDK interface.
> > If the user set one of 'spec' and 'mask', we will also set 'spec' '0000' and mask 'ffff' write fd table to HW.
> > This is how we handle it.
> Understood. But is this the best course of action? Say, what happens if the user
> passes ETH / IPV4 / UDP pattern items, where 'spec' and 'mask' are 'null' in all
> the items? Theoretically, the driver could translate this to set the key to have
> EtherType 0x0800/0xffff and IP protocol to be 0x11/0xff . Or am I wrong?
> Thank you.
Yes, you are right. Currently, our plan is not optimal, and we will take your suggestions as a reference.
If there are any optimizations in the future, we will resubmit it.
Thank you very much.
[-- Attachment #1.1.2: Type: text/html , Size: 2907 bytes --]
prev parent reply other threads:[~2025-08-12 10:57 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-17 9:31 [PATCH v1 0/2] " Bingbin Chen
2025-06-17 9:32 ` [PATCH v1 1/2] net/zxdh: npsdk add flow director table ops Bingbin Chen
2025-06-17 14:07 ` Stephen Hemminger
2025-06-17 14:08 ` Stephen Hemminger
2025-06-17 9:32 ` [PATCH v1 2/2] net/zxdh: add support flow director ops Bingbin Chen
2025-06-18 7:49 ` [PATCH v2 0/2] " Bingbin Chen
2025-06-18 7:49 ` [PATCH v2 1/2] net/zxdh: npsdk add flow director table ops Bingbin Chen
2025-06-18 7:49 ` [PATCH v2 2/2] net/zxdh: add support flow director ops Bingbin Chen
2025-06-30 16:56 ` Stephen Hemminger
2025-07-02 7:34 ` [PATCH v3 0/2] " Bingbin Chen
2025-07-02 7:34 ` [PATCH v3 1/2] net/zxdh: npsdk add flow director table ops Bingbin Chen
2025-07-02 7:34 ` [PATCH v3 2/2] net/zxdh: add support flow director ops Bingbin Chen
2025-07-02 15:02 ` Stephen Hemminger
2025-08-03 17:34 ` Stephen Hemminger
2025-08-08 7:10 ` [PATCH v4 0/2] " Junlong Wang
2025-08-08 7:10 ` [PATCH v4 1/2] net/zxdh: npsdk add flow director table ops Junlong Wang
2025-08-08 7:10 ` [PATCH v4 2/2] net/zxdh: add support flow director ops Junlong Wang
2025-08-08 9:15 ` Ivan Malov
2025-08-08 16:12 ` Stephen Hemminger
2025-08-12 1:23 ` [v4,2/2] " Junlong Wang
2025-08-12 4:04 ` Ivan Malov
2025-08-12 7:19 ` Junlong Wang
2025-08-12 7:36 ` Ivan Malov
2025-08-12 10:47 ` Junlong Wang [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=20250812104703.2111951-1-wang.junlong1@zte.com.cn \
--to=wang.junlong1@zte.com.cn \
--cc=chen.bingbin@zte.com.cn \
--cc=dev@dpdk.org \
--cc=ivan.malov@arknetworks.am \
--cc=stephen@networkplumber.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).