From: Ivan Boule <ivan.boule@6wind.com>
To: Michael Quicquaro <michael.quicquaro@gmail.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] Redirection Table
Date: Mon, 06 Jan 2014 16:21:59 +0100 [thread overview]
Message-ID: <52CACA17.7000202@6wind.com> (raw)
In-Reply-To: <CAAD-K95hrqcCT=fO-4h36KBSZJrvoPjJVNtf+4JtG6R2QYmR7w@mail.gmail.com>
On 12/31/2013 08:45 PM, Michael Quicquaro wrote:
> Has anyone used the "port config all reta (hash,queue)" command of testpmd
> with any success?
>
> I haven't found much documentation on it.
>
> Can someone provide an example on why and how it was used.
>
> Regards and Happy New Year,
> Michael Quicquaro
Hi Michael,
"RETA" stands for Redirection Table.
It is a per-port configurable table of 128 entries that is used by the
RSS filtering feature of Intel 1GbE and 10GbE controllers to select the
RX queue into which to store a received IP packet.
When receiving an IPv4/IPv6 packet, the controller computes a 32-bit
hash on:
* the source address and the destination address of the IP header of
the packet,
* the source port and the destination port of the UDP/TCP header, if any.
Then, the controller takes the 7 lower bits of the RSS hash as an index
into the RETA table to get the RX queue number where to store the packet.
The API of the DPDK includes a function that is exported by Poll Mode
Drivers to configure RETA entries of a given port.
For test purposes, the testpmd application includes the following command
"port config X rss reta (hash,queue)[,(hash,queue)]"
to configure RETA entries of a port X, with each couple (hash,queue)
contains the index of a RETA entry (between 0 and 127 included) and the
RX queue number (between 0 and 15) to be stored into that RETA entry.
Best regards
Ivan
--
Ivan Boule
6WIND Development Engineer
next prev parent reply other threads:[~2014-01-06 15:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-31 19:45 Michael Quicquaro
2014-01-06 15:21 ` Ivan Boule [this message]
2014-01-06 16:52 ` Michael Quicquaro
2014-01-07 8:35 ` Ivan Boule
2014-01-07 13:03 ` Stefan Baranoff
2014-01-10 10:14 ` Ivan Boule
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=52CACA17.7000202@6wind.com \
--to=ivan.boule@6wind.com \
--cc=dev@dpdk.org \
--cc=michael.quicquaro@gmail.com \
/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).