From: oulijun <oulijun@huawei.com>
To: Ophir Munk <ophirmu@nvidia.com>,
Ferruh Yigit <ferruh.yigit@intel.com>,
"wenzhuo.lu@intel.com" <wenzhuo.lu@intel.com>,
"beilei.xing@intel.com" <beilei.xing@intel.com>,
NBU-Contact-Adrien Mazarguil <adrien.mazarguil@6wind.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
"linuxarm@huawei.com" <linuxarm@huawei.com>,
Ori Kam <orika@nvidia.com>
Subject: Re: [dpdk-dev] [PATCH v5] app/testpmd: fix the default RSS key configuration
Date: Fri, 16 Oct 2020 18:05:32 +0800 [thread overview]
Message-ID: <21dfaee9-0a63-c154-779a-c932715ae6dd@huawei.com> (raw)
In-Reply-To: <DM5PR12MB11615D226BE211FDD30A613ADC030@DM5PR12MB1161.namprd12.prod.outlook.com>
在 2020/10/16 14:46, Ophir Munk 写道:
>
>
>> -----Original Message-----
>> From: Ferruh Yigit <ferruh.yigit@intel.com>
> <..>
>>>>
>>>
>>> Ferruh, your suggestion ([1] + update) looks correct. I also verified it on
>> mlx5 PMD.
>>> Advantage: it's a generic fix for all dpdk applications using rte_flows (not
>> just testpmd).
>>> It reduces code.
>>> With this fix the responsibility of handling key==NULL and/or len==0 is
>> moved to the PMDs (which is good).
>>>
>>> With regard to Lijun patch - I liked the approach of overriding the default
>> testpmd key with the default PMD key.
>>> But it only addresses testpmd. More code was added.
>>> It seems OK to call rte_eth_dev_rss_hash_conf_get() as part of parsing
>> RSS, but it would feel more confident if we could confirm it for all the PMDs
>> (by testing) or at least review the PMDs rss_hash_conf_get()
>> implementations.
>>>
>>
>> Lijun's idea can work. There was a problem in implementation related to the
>> key size assumption, which can be fixed.
>>
>> Even it is fixed, when user gives a rss rule without a key, we are getting key
>> from device and feeding same key back to device, this is unnecessary I think.
>
> I agree.
>
>> When user didn't provide a key, rss rule shouldn't touch the key at all.
>
> Agreed as well.
>
>> Complication was when user provides key_len without a key, I think both
>> ignoring or returning error in this case is OK.
>
> I think that in general flow rules should arrive "as is" to the PMD which has its
> validation and translation APIs to handle all cases.
>
Do you agree with [1] + Ferruh update solution?
next prev parent reply other threads:[~2020-10-16 10:05 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-10 1:51 [dpdk-dev] [PATCH v3] " Lijun Ou
2020-09-22 9:51 ` Phil Yang
2020-09-22 13:50 ` oulijun
2020-09-22 15:44 ` Phil Yang
2020-09-24 13:45 ` [dpdk-dev] [PATCH v4] RSS key use with testpmd Lijun Ou
2020-09-24 13:45 ` [dpdk-dev] [PATCH v4] app/testpmd: fix the default RSS key configuration Lijun Ou
2020-09-29 15:35 ` Phil Yang
2020-09-30 12:57 ` Ferruh Yigit
2020-10-09 11:55 ` oulijun
2020-10-09 18:27 ` Ferruh Yigit
2020-10-09 18:54 ` Ferruh Yigit
2020-09-30 13:36 ` Ferruh Yigit
2020-10-09 11:59 ` oulijun
2020-10-09 18:36 ` Ferruh Yigit
2020-10-15 12:41 ` [dpdk-dev] [PATCH v5] " Lijun Ou
2020-10-15 13:52 ` Ferruh Yigit
2020-10-15 14:04 ` oulijun
2020-10-15 14:43 ` Ferruh Yigit
2020-10-15 16:05 ` Ferruh Yigit
2020-10-15 23:21 ` Ophir Munk
2020-10-15 23:53 ` Ferruh Yigit
2020-10-16 0:14 ` Ajit Khaparde
2020-10-16 6:46 ` Ophir Munk
2020-10-16 10:05 ` oulijun [this message]
2020-10-16 15:13 ` Ophir Munk
2020-10-16 10:04 ` oulijun
2020-10-16 10:57 ` Ferruh Yigit
2020-10-16 14:59 ` Ophir Munk
2020-10-20 9:00 ` oulijun
2020-10-20 10:02 ` Ferruh Yigit
2020-10-20 13:35 ` oulijun
2020-10-20 14:34 ` Ferruh Yigit
2020-10-21 8:19 ` oulijun
2020-10-21 9:38 ` Ferruh Yigit
2020-10-21 10:07 ` oulijun
[not found] ` <20201015195637.26476-1-robot@bytheb.org>
2020-10-16 9:39 ` [dpdk-dev] |WARNING| pw80899 " oulijun
2020-10-16 9:41 ` David Marchand
2020-09-30 13:17 ` [dpdk-dev] [PATCH v4] RSS key use with testpmd Ferruh Yigit
2020-10-09 12:09 ` oulijun
2020-10-09 18:52 ` Ferruh Yigit
2020-10-10 3:07 ` Phil Yang
2020-10-14 6:15 ` oulijun
2020-10-14 8:41 ` Ferruh Yigit
2020-10-15 12:30 [dpdk-dev] [PATCH v5] app/testpmd: fix the default RSS key configuration Lijun Ou
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=21dfaee9-0a63-c154-779a-c932715ae6dd@huawei.com \
--to=oulijun@huawei.com \
--cc=adrien.mazarguil@6wind.com \
--cc=beilei.xing@intel.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=linuxarm@huawei.com \
--cc=ophirmu@nvidia.com \
--cc=orika@nvidia.com \
--cc=wenzhuo.lu@intel.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).