DPDK usage discussions
 help / color / mirror / Atom feed
From: Jay Miller <jay.miller@oracle.com>
To: users@dpdk.org
Subject: [dpdk-users] Support for more RSS hash types in vmxnet3
Date: Tue, 21 Aug 2018 13:57:08 -0400	[thread overview]
Message-ID: <6033fde3-997d-df67-feee-d6a501b9b4be@oracle.com> (raw)
In-Reply-To: <1e5ecad5-79d4-490f-5c79-f508bd4c1800@oracle.com>

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?

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

-- 
Jay Miller | Mobile: +1.781.258.7446
Oracle Communications Global Business Unit
100 Crosby Drive | Bedford, MA 01730

  reply	other threads:[~2018-08-21 17:57 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 ` Jay Miller [this message]
2018-08-21 18:22   ` [dpdk-users] Support for more RSS hash types in vmxnet3 Stephen Hemminger
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=6033fde3-997d-df67-feee-d6a501b9b4be@oracle.com \
    --to=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).