From: Stephen Hemminger <stephen@networkplumber.org>
To: Jay Miller <jay.miller@oracle.com>
Cc: users@dpdk.org
Subject: Re: [dpdk-users] Support for more RSS hash types in vmxnet3
Date: Tue, 21 Aug 2018 11:22:32 -0700 [thread overview]
Message-ID: <20180821112232.1549773f@xeon-e3> (raw)
In-Reply-To: <6033fde3-997d-df67-feee-d6a501b9b4be@oracle.com>
On Tue, 21 Aug 2018 13:57:08 -0400
Jay Miller <jay.miller@oracle.com> wrote:
> It's clear that the vmxnet3 driver (even as of 18.08) supports just a
> subset of RSS hash types:
>
> #define VMXNET3_RSS_OFFLOAD_ALL ( \
> ETH_RSS_IPV4 | \
> ETH_RSS_NONFRAG_IPV4_TCP | \
> ETH_RSS_IPV6 | \
> ETH_RSS_NONFRAG_IPV6_TCP)
>
> Are there plans to add support for other hash types (like
> ETH_RSS_NONFRAG_IPV4_UDP), or is this an architectural limitation of
> vmxnet3?
Did you test, I suspect that VMWare supports that already.
The values in the API to the host are:
/* value of RxCompDesc.rssType */
enum {
VMXNET3_RCD_RSS_TYPE_NONE = 0,
VMXNET3_RCD_RSS_TYPE_IPV4 = 1,
VMXNET3_RCD_RSS_TYPE_TCPIPV4 = 2,
VMXNET3_RCD_RSS_TYPE_IPV6 = 3,
VMXNET3_RCD_RSS_TYPE_TCPIPV6 = 4,
};
> The documentation could be more explicit about these limitations:
>
> >>
> >> 36.2. Features and Limitations of VMXNET3 PMD
> >>
> >> In release 1.6.0, the VMXNET3 PMD provides the basic functionality of
> >> packet reception and transmission. There are several options
> >> available for filtering packets at VMXNET3 device level including:
> >>
> >> 1. *MAC Address based filtering*:
> >> * Unicast, Broadcast, All Multicast modes - SUPPORTED BY DEFAULT
> >> * Multicast with Multicast Filter table - NOT SUPPORTED
> >> * Promiscuous mode - SUPPORTED
> >> * *RSS based load balancing between queues - SUPPORTED*
> >>
> >
>
> Thanks,
> J
>
next prev parent reply other threads:[~2018-08-21 18:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-21 14:03 [dpdk-users] vmxnet3 RSS implementation Jay Miller
2018-08-21 17:57 ` [dpdk-users] Support for more RSS hash types in vmxnet3 Jay Miller
2018-08-21 18:22 ` Stephen Hemminger [this message]
2018-08-22 9:55 ` Ferruh Yigit
2018-09-13 22:44 ` Yong Wang
2019-03-18 13:58 ` Iain Barker
2019-03-18 20:09 ` Yong Wang
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=20180821112232.1549773f@xeon-e3 \
--to=stephen@networkplumber.org \
--cc=jay.miller@oracle.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).