From: Ferruh Yigit <ferruh.yigit@amd.com>
To: madhuker.mythri@oracle.com, Ophir Munk <ophirmu@nvidia.com>
Cc: dev@dpdk.org, sthemmin@microsoft.com,
Thomas Monjalon <thomas@monjalon.net>
Subject: Re: [PATCH] net/tap: Fixed RSS algorithm to support fragmented packets
Date: Thu, 19 Jan 2023 12:03:59 +0000 [thread overview]
Message-ID: <ed10417d-489f-cf53-cc50-4fd35714eefc@amd.com> (raw)
In-Reply-To: <20220420112400.2271-1-madhuker.mythri@oracle.com>
On 4/20/2022 12:24 PM, madhuker.mythri@oracle.com wrote:
> From: Madhuker Mythri <madhuker.mythri@oracle.com>
>
> As per analysis on Tap PMD, the existing RSS algorithm considering
> 4-tuple(Src-IP, Dst-IP, Src-port and Dst-port) and identification of
> fragment packets is not done, thus we are seeing all the fragmented
> chunks of single packet differs in RSS hash value and distributed across
> multiple queues.
> The RSS algorithm assumes that, all the incoming IP packets are based on
> L4-protocol(UDP/TCP) and trying to fetch the L4 fields(Src-port and
> Dst-port) for each incoming packet, but for the fragmented chunks these
> L4-header will not be present(except for first packet) and should not
> consider in RSS hash for L4 header fields in-case of fragmented chunks.
> Which is a bug in the RSS algorithm implemented in the BPF functionality
> under TAP PMD.
>
> So, modified the RSS eBPF C-program and generated the structure of
> C-array in the 'tap_bpf_insns.h' file, which is in eBPF byte-code
> instructions format.
>
> Bugzilla Id: 870
>
> Signed-off-by: Madhuker Mythri <madhuker.mythri@oracle.com>
> ---
> drivers/net/tap/tap_bpf_insns.h | 3371 +++++++++++++++--------------
> drivers/net/tap/tap_bpf_program.c | 47 +-
> 2 files changed, 1742 insertions(+), 1676 deletions(-)
Hi Ophir,
Original files from you, can you please help to review this patch?
For reference, this is in patchwork:
https://patches.dpdk.org/project/dpdk/patch/20220420112400.2271-1-madhuker.mythri@oracle.com/
Thanks,
ferruh
next prev parent reply other threads:[~2023-01-19 12:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-20 11:24 madhuker.mythri
2023-01-19 12:03 ` Ferruh Yigit [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-03-25 15:28 madhuker.mythri
2022-06-03 15:53 ` Stephen Hemminger
2022-06-03 16:21 ` 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=ed10417d-489f-cf53-cc50-4fd35714eefc@amd.com \
--to=ferruh.yigit@amd.com \
--cc=dev@dpdk.org \
--cc=madhuker.mythri@oracle.com \
--cc=ophirmu@nvidia.com \
--cc=sthemmin@microsoft.com \
--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).