From: kumaraparameshwaran rathinavel <kumaraparamesh92@gmail.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: dev <dev@dpdk.org>
Subject: Re: [PATCH] net/tap: add deprecation notice for RTE_FLOW_ACTION_RSS
Date: Fri, 15 Dec 2023 10:28:06 +0530 [thread overview]
Message-ID: <CANxNyasmyCwaF+-+42CCnfQ3f+PEK4KnUWH+k6yabVSoq7hMJA@mail.gmail.com> (raw)
In-Reply-To: <20231214190119.7bb28203@hermes.local>
[-- Attachment #1: Type: text/plain, Size: 1313 bytes --]
On Fri, Dec 15, 2023, 8:31 AM Stephen Hemminger <stephen@networkplumber.org>
wrote:
> On Fri, 15 Dec 2023 00:18:41 +0530
> kumaraparameshwaran rathinavel <kumaraparamesh92@gmail.com> wrote:
>
> > On Thu, Dec 14, 2023, 11:20 PM Stephen Hemminger <
> stephen@networkplumber.org>
> > wrote:
> >
> > > The BPF infrastructure in kernel changed which broke the method
> > > being used to load the RSS part of rte_flow in the TAP device.
> > > Since this is a little used feature, and fixing the problem would
> > > be moderately complex and create new dependency on libbpf,
> > > mark the feature as deprecated and plan for removal.
> >
> > Does this mean that RSS will not work with netvsc as netvsc is using
> > tap and mellanox ? Or will that not be affected .
>
>
> The netvsc driver does not support rte_flow because the packets arrive
> direct from host (over vmbus). It does have normal RSS.
> It many ways netvsc is equivalent in functionality to virtio and vmxnet3.
>
> The tap BPF stuff was only useful for doing flow steering to a set of
> queues. It was a hack to get the kernel to do flow steering.
>
Sure. I wanted to mean that the failsafe PMD that uses tap and mellanox
relies on offloads of both the devices. So will this cause failsafe PMD to
not use RSS and hence some performance impact ?
>
[-- Attachment #2: Type: text/html, Size: 2109 bytes --]
next prev parent reply other threads:[~2023-12-15 4:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-14 17:49 Stephen Hemminger
2023-12-14 18:03 ` Ferruh Yigit
2023-12-14 18:48 ` kumaraparameshwaran rathinavel
2023-12-15 3:01 ` Stephen Hemminger
2023-12-15 4:58 ` kumaraparameshwaran rathinavel [this message]
2023-12-15 3:57 ` Stephen Hemminger
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=CANxNyasmyCwaF+-+42CCnfQ3f+PEK4KnUWH+k6yabVSoq7hMJA@mail.gmail.com \
--to=kumaraparamesh92@gmail.com \
--cc=dev@dpdk.org \
--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).