From: Rob Zimmerman <rob@thezims.net>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: users@dpdk.org
Subject: Re: [dpdk-users] RSS RETA size of 0 on vmxnet3?
Date: Fri, 27 Jan 2017 18:21:10 -0500 [thread overview]
Message-ID: <CAG0K5qtyT00vmTEFa_ZQErmBnquJ51ffEtFtxm58pz7PnSmHgQ@mail.gmail.com> (raw)
In-Reply-To: <20170127140308.3855cbd2@xeon-e3>
Thanks for the reply, @networkplumber :)
No KNI interface here, unfortunately. Just a plain-ol DPDK ethernet device.
In the scenario where the RETA size is 0 I'm using the vmxnet3_pmd. Within
the application the eth devices are initialized and I make a call to
rte_eth_dev_info_get().
What is everyone else seeing for the RETA size using vmxnet3?
Thanks again everyone,
~Rob
On Fri, Jan 27, 2017 at 5:03 PM, Stephen Hemminger <
stephen@networkplumber.org> wrote:
> On Fri, 27 Jan 2017 14:53:22 -0500
> Rob Zimmerman <rob@thezims.net> wrote:
>
> > Happy Friday, everyone!
> >
> > Testing within VMWARE and my device query is showing the following:
> >
> > RSS Offload
> > - reta size: 0
> > - IPv4: yes
> > - TCP: yes
> > - UDP: no
> > - SCTP: no
> > - IPv6: yes
> > ....
> >
> > How exactly does RSS work with a table size of zero? Unless I'm
> completely
> > misunderstanding how to use RSS, I thought the redirection table was
> > instrumental to that process...
> >
> > FWIW, I'm running the same code on a bare-metal box with Intel I350's
> > (igb_pmd) and it's showing a RETA size of 128, so I don't think it's my
> > code showing a junk value.
> >
> > Thanks!
> > Rob
>
> If you are querying a KNI interface (ie through Linux), it just means
> the KNI interface doesn't do the ethtool support that value.
>
next prev parent reply other threads:[~2017-01-27 23:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-27 19:53 Rob Zimmerman
2017-01-27 22:03 ` Stephen Hemminger
2017-01-27 23:21 ` Rob Zimmerman [this message]
2017-01-28 0:07 ` Stephen Hemminger
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=CAG0K5qtyT00vmTEFa_ZQErmBnquJ51ffEtFtxm58pz7PnSmHgQ@mail.gmail.com \
--to=rob@thezims.net \
--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).