From: "Chilikin, Andrey" <andrey.chilikin@intel.com>
To: sasidhar reddy <sasidhar.yellaturi@gmail.com>,
"users@dpdk.org" <users@dpdk.org>
Subject: Re: [dpdk-users] RSS distribution of Encapsulated packets
Date: Tue, 11 Jun 2019 08:58:15 +0000 [thread overview]
Message-ID: <AAC06825A3B29643AF5372F5E0DDF0538E35CF1B@IRSMSX106.ger.corp.intel.com> (raw)
In-Reply-To: <CAJ2QouddowqdG4qYTO8n9itr3y3qoxAvZ1drvXJmMHyfdawcjw@mail.gmail.com>
Hi Sashi,
There could be a few solutions, depending on how your encapsulation is implemented:
* flexible payload to extract up to 16 bytes from the packet for RSS: works for L2/L3/L4 payloads
* special configuration of L2 tags: works for headers with the specific Ethertypes
* Dynamic Device Personalization (DDP): reprograming parser to understand new L2/L3/L4 protocols
Regards,
Andrey
-----Original Message-----
From: users [mailto:users-bounces@dpdk.org] On Behalf Of sasidhar reddy
Sent: Monday, June 10, 2019 12:29 PM
To: users@dpdk.org
Subject: [dpdk-users] RSS distribution of Encapsulated packets
Hi,
Our application needs to process encapsulated packets(Custom encapsulation,
adding our proprietary header to packets). NIC RSS is not distributing the
packets across all the cores(queues) setup. Packets are always landing in a
single core(default core). We are not looking at software based
distribution due to scalability.
1) Is there any way to use RSS/VMDQ to serve this purpose at NIC?
2) Can we configure NIC to perform round robin distribution?
Note:
We use XL710 NIC
Regards,
Sashi
prev parent reply other threads:[~2019-06-11 8:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-10 11:29 sasidhar reddy
2019-06-11 8:58 ` Chilikin, Andrey [this message]
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=AAC06825A3B29643AF5372F5E0DDF0538E35CF1B@IRSMSX106.ger.corp.intel.com \
--to=andrey.chilikin@intel.com \
--cc=sasidhar.yellaturi@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).