From: Stephen Hemminger <stephen@networkplumber.org>
To: cs cs <pacman.n908@gmail.com>
Cc: users@dpdk.org
Subject: Re: [dpdk-users] Packet distribution of single flow type using DPDK in Mellanox ConnectX-5 Ex
Date: Tue, 31 Aug 2021 19:17:54 -0700 [thread overview]
Message-ID: <20210831191754.5eba7b26@hermes.local> (raw)
In-Reply-To: <CALgGc3VyuS=A41uyuw4m3q+mv74EReOBn_Hcd6e6se=dEG5+SA@mail.gmail.com>
On Tue, 31 Aug 2021 18:28:12 -0700
cs cs <pacman.n908@gmail.com> wrote:
> Hi,
>
> Is there a way in DPDK to configure Mellanox ConnectX-5 Ex to distribute
> the incoming packets of a single flow type to multiple NIC hardware queues?
Yes, use rte_flow and rte_flow_action_type_rss.
> Does ConnectX-5 Ex PMD support constantly changing the RETA table during
> runtime without having to stop and start the device for the table to get
> updated and for the packets to get dispatched to multiple cores? Could this
> be a possible solution?
The Reta table is only used without rte_flow.
Use rte_flow it is a better solution.
prev parent reply other threads:[~2021-09-01 2:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-01 1:28 cs cs
2021-09-01 2:17 ` Stephen Hemminger [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=20210831191754.5eba7b26@hermes.local \
--to=stephen@networkplumber.org \
--cc=pacman.n908@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).