From: Muhammad Zain-ul-Abideen <zain2294@gmail.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: Raslan Darawsheh <rasland@nvidia.com>,
madhukar mythri <madhukar.mythri@gmail.com>,
users <users@dpdk.org>
Subject: Re: [dpdk-users] Issue with UDP based fragmented packets on Azure cloud
Date: Fri, 28 May 2021 11:51:56 +0500 [thread overview]
Message-ID: <CAN7yQ2oCwsjU0addKX9Uev5upm7Xd9+_QuWyguQowrm_ahRnzw@mail.gmail.com> (raw)
In-Reply-To: <20210527125703.059eeead@hermes.local>
I wonder is there any way to bypass RSS for some IP flag values like mf, or
frag_offset
On Fri, May 28, 2021, 12:57 AM Stephen Hemminger <stephen@networkplumber.org>
wrote:
> On Thu, 27 May 2021 15:40:57 +0000
> Raslan Darawsheh <rasland@nvidia.com> wrote:
>
> > 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.
> > >
>
> Yes, and this is not unique to Azure or even the DPDK.
> Fragmented packets do not have enough information (no UDP header in second
> fragment)
> to do L4 RSS.
>
>
next prev parent reply other threads:[~2021-05-28 6:52 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
2021-05-27 19:57 ` Stephen Hemminger
2021-05-28 6:51 ` Muhammad Zain-ul-Abideen [this message]
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=CAN7yQ2oCwsjU0addKX9Uev5upm7Xd9+_QuWyguQowrm_ahRnzw@mail.gmail.com \
--to=zain2294@gmail.com \
--cc=madhukar.mythri@gmail.com \
--cc=rasland@nvidia.com \
--cc=stephen@networkplumber.org \
--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).