From: Raslan Darawsheh <rasland@nvidia.com>
To: madhukar mythri <madhukar.mythri@gmail.com>,
"users@dpdk.org" <users@dpdk.org>
Subject: Re: [dpdk-users] Issue with UDP based fragmented packets on Azure cloud
Date: Thu, 27 May 2021 15:40:57 +0000 [thread overview]
Message-ID: <DM4PR12MB5054ADA6406B1C90F6ACE5C5CF239@DM4PR12MB5054.namprd12.prod.outlook.com> (raw)
In-Reply-To: <CAAUNki1XiOv3VMQZZpF0TOGWMYf+PpGZgpVg8iXom3nXqTkYqw@mail.gmail.com>
Hi,
> -----Original Message-----
> From: users <users-bounces@dpdk.org> On Behalf Of madhukar mythri
> Sent: Thursday, May 27, 2021 5:58 PM
> To: users@dpdk.org
> Subject: [dpdk-users] Issue with UDP based fragmented packets on Azure
> cloud
>
> Hi,
>
> We are facing issue with UDP/IP based fragmented packets on Azure cloud
> platform with Accelerated-Network enabled ports.
>
> UDP fragmented Rx packets were able to receive well on media ports. But,
> when two fragmented packet received, first fragment is received on Queue-
> 0
> and second fragment is received on Queue-1. Ideally all the fragments(of
> single large packet) should be received single queue based on RSS, so that
> we can re-assemble as single pkt and process it, which is working well in
> other platforms on KVM hyper-visors(with I40evf NIC’s).
>
> I think, the as per RSS hash cacluation all the fragmented pkts should
> reach on single-queue(because the 5-tuple hash value will be same), but
> this is not happening in-case of Azue VM's Why ?
>
> Does anybody faced similar issue, please let me know your suggestion.
I guess it depends on the fragments themselves,
If your first fragment contains a UDP header (the first frag in the list) then the RSS hash will be on the full 5 tuble
Src/dst IP and src/dst udp
But, for the other frags you'll not get src/dst udp since they are not present in the pkt.
I guess you should be using only RSS On IP header to make all frags go to the same queue.
>
> Thanks,
> Madhukar.
Kindest regards,
Raslan Darawsheh
next prev parent reply other threads:[~2021-05-27 15:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-27 14:57 madhukar mythri
2021-05-27 15:40 ` Raslan Darawsheh [this message]
2021-05-27 19:57 ` Stephen Hemminger
2021-05-28 6:51 ` Muhammad Zain-ul-Abideen
2021-05-28 10:24 ` madhukar mythri
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=DM4PR12MB5054ADA6406B1C90F6ACE5C5CF239@DM4PR12MB5054.namprd12.prod.outlook.com \
--to=rasland@nvidia.com \
--cc=madhukar.mythri@gmail.com \
--cc=users@dpdk.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).