DPDK patches and discussions
 help / color / mirror / Atom feed
From: "lihuisong (C)" <lihuisong@huawei.com>
To: "orika@nvidia.com >> Ori Kam" <orika@nvidia.com>,
	"dev@dpdk.org" <dev@dpdk.org>
Cc: Stephen Hemminger <stephen@networkplumber.org>,
	Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>,
	Thomas Monjalon <thomas@monjalon.net>,
	Ferruh Yigit <ferruh.yigit@xilinx.com>,
	huangdaode <huangdaode@huawei.com>,
	"fengchengwen@huawei.com" <fengchengwen@huawei.com>,
	"liudongdong (C)" <liudongdong3@huawei.com>
Subject: Re: Question about pattern types for rte_flow RSS rule
Date: Wed, 13 Jul 2022 09:34:09 +0800	[thread overview]
Message-ID: <ca2daf37-1c6b-e661-fb4a-845c3d679bc3@huawei.com> (raw)
In-Reply-To: <8c5019cf-312e-708a-d1d5-cba666443f87@huawei.com>

Hi all,

Can someone open my confusion?
I'm looking forward to your reply.

Thanks,
Huisong.

在 2022/7/7 11:50, lihuisong (C) 写道:
> Hi all,
>
> From following testpmd command:
> 'flow create 0 ingress pattern eth / ipv4 / tcp / end actions rss 
> types ipv4-tcp l3-src-only end queues end / end'
> and
> "flow create 0 ingress pattern end actions rss types ipv4-tcp 
> l3-src-only end queues end / end"
>
> I have some confusions about rte_flow RSS rule:
> 1> Do pattern item types need to set when configure rte_flow RSS rule?
> 2> Does the driver need to check and process the pattern? (After all, 
> the RSS types in actions alreadly contain all RSS offload types.)
>
> Have someone explains it?
>
> Regards,
> Huisong
>
> .

  reply	other threads:[~2022-07-13  1:34 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-07  3:50 lihuisong (C)
2022-07-13  1:34 ` lihuisong (C) [this message]
2022-07-29  2:30   ` lihuisong (C)
2022-07-31  9:40     ` Andrew Rybchenko
2022-08-01  3:39       ` lihuisong (C)
2022-08-01 11:53         ` Andrew Rybchenko
2022-08-01 13:27           ` lihuisong (C)
2022-08-01 14:12             ` Andrew Rybchenko
2022-08-02  1:27               ` lihuisong (C)

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=ca2daf37-1c6b-e661-fb4a-845c3d679bc3@huawei.com \
    --to=lihuisong@huawei.com \
    --cc=andrew.rybchenko@oktetlabs.ru \
    --cc=dev@dpdk.org \
    --cc=fengchengwen@huawei.com \
    --cc=ferruh.yigit@xilinx.com \
    --cc=huangdaode@huawei.com \
    --cc=liudongdong3@huawei.com \
    --cc=orika@nvidia.com \
    --cc=stephen@networkplumber.org \
    --cc=thomas@monjalon.net \
    /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).