From: "Samudrala, Sridhar" <sridhar.samudrala@intel.com>
To: "huangguangbin (A)" <huangguangbin2@huawei.com>,
Jakub Kicinski <kuba@kernel.org>
Cc: <davem@davemloft.net>, <idosch@nvidia.com>,
<linux@rempel-privat.de>, <mkubecek@suse.cz>,
<netdev@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<lipeng321@huawei.com>, <shenjian15@huawei.com>,
"Nambiar, Amritha" <amritha.nambiar@intel.com>
Subject: Re: [PATCH net-next 0/2] net: ethtool add VxLAN to the NFC API
Date: Mon, 22 Aug 2022 10:48:10 -0500 [thread overview]
Message-ID: <5b397d3b-5a5d-e226-dc47-f4333a9cacf9@intel.com> (raw)
In-Reply-To: <5062c7ae-3415-adf6-6488-f9a05177d2c2@huawei.com>
On 8/22/2022 9:46 AM, huangguangbin (A) wrote:
>
>
> On 2022/8/18 2:16, Jakub Kicinski wrote:
>> On Wed, 17 Aug 2022 22:35:36 +0800 Guangbin Huang wrote:
>>> This series adds support for steering VxLAN flows using the ethtool NFC
>>> interface, and implements it for hns3 devices.
>>
>> Why can't TC be used for this? Let's not duplicate the same
>> functionality in two places, TC flower can already match on
>> tunnel headers.
>> .
>>
> Hi Jakub,
> 1. I check the manual and implement of TC flower, it doesn't seems
> to support configuring flows steering to a specific queue.
Based on the discussion in this email thread
https://lore.kernel.org/netdev/20220429171717.5b0b2a81@kernel.org/
Amritha will be submitting a patch series soon to enable redirecting to
a RX qeueue
via tc flower using skbedit queue_mapping action offload.
- Sridhar
next prev parent reply other threads:[~2022-08-22 15:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-17 14:35 Guangbin Huang
2022-08-17 14:35 ` [PATCH net-next 1/2] net: ethtool: " Guangbin Huang
2022-08-17 14:35 ` [PATCH net-next 2/2] net: hns3: support set/get VxLAN rule of rx flow director by ethtool Guangbin Huang
2022-08-17 18:16 ` [PATCH net-next 0/2] net: ethtool add VxLAN to the NFC API Jakub Kicinski
2022-08-22 14:46 ` huangguangbin (A)
2022-08-22 15:48 ` Samudrala, Sridhar [this message]
2022-08-22 16:53 ` Jakub Kicinski
2022-08-23 8:20 ` huangguangbin (A)
2026-04-09 4:03 ` Jijie Shao
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=5b397d3b-5a5d-e226-dc47-f4333a9cacf9@intel.com \
--to=sridhar.samudrala@intel.com \
--cc=amritha.nambiar@intel.com \
--cc=davem@davemloft.net \
--cc=huangguangbin2@huawei.com \
--cc=idosch@nvidia.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@rempel-privat.de \
--cc=lipeng321@huawei.com \
--cc=mkubecek@suse.cz \
--cc=netdev@vger.kernel.org \
--cc=shenjian15@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome