From: Liwu Liu <liwuliu@fortinet.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: "users@dpdk.org" <users@dpdk.org>
Subject: Re: [dpdk-users] Cannot run DPDK applications using Mellanox NIC under Hyper-V
Date: Tue, 8 Jan 2019 18:38:41 +0000 [thread overview]
Message-ID: <a064008d85da4aeba554252e57dac005@fortinet.com> (raw)
In-Reply-To: <20190104170802.4ed27cce@hermes.lan>
Updates: many thanks for MLNX engineering team, doing the following can resolve this issue:
1- On power shell: "Set-VMNetworkAdapter -VMName <VM_NAME> -Name "Network Adapter" -IovQueuePairsRequested 64"
2- In the registry editor, make sure that you increase the ExtraVFsQuotas percentage to be 1000 to use full resources.
HKEY_LOCAL_MACHINE \SYSTEM\CurrentControlSet\Control\Class\{4d36e97d-e325-11ce-bfc1- 08002be10318}\<nn>\Parameters
3- BlockFlowsForPerformance registry key:
HKEY_LOCAL_MACHINE \SYSTEM\CurrentControlSet\Control\Class\{4d36e97d-e325-11ce-bfc1- 08002be10318}\<nn>\Parameters
When the BlockFlowsForPerformance registry is set to 1, by default only L4 rules are allowed to be configured with rte_flow API.
When the BlockFlowsForPerformance is set to 0, then L3 and L4 rules are allowed.
-----Original Message-----
From: Stephen Hemminger <stephen@networkplumber.org>
Sent: Friday, January 4, 2019 5:08 PM
To: Liwu Liu <liwuliu@fortinet.com>
Cc: users@dpdk.org
Subject: Re: [dpdk-users] Cannot run DPDK applications using Mellanox NIC under Hyper-V
On Sat, 5 Jan 2019 00:35:13 +0000
Liwu Liu <liwuliu@fortinet.com> wrote:
> Hi Stephen,
>
> Yeah we are seeing all NETVSC, failsafe PMD, TAP, MLX4 VF. We are expecting bifurcation mode where default traffic goes with MLX4_EN slave to NETVSC master to enter Linux net stack and certain flow-defined traffic shall go into DPDK RX queue rather than MLX4_EN net-dev queue. Unfortunately as we cannot define flow into VF NIC, we cannot re-direct traffic into DPDK user-land.
This is a little more complex.
You need to use rte_flow on the failsafe PMD and that is supposed to get propogated to TAP and MLX VF.
The TAP PMD programs BPF in kernel, and the MLX VF PMD programs the VF flow tables.
Haven't tried it myself.
next prev parent reply other threads:[~2019-01-08 18:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-04 20:06 Liwu Liu
2019-01-05 0:06 ` Stephen Hemminger
2019-01-05 0:12 ` Liwu Liu
[not found] ` <596318879eb14b32971e4c182489f537@fortinet.com>
[not found] ` <20190104162349.264da710@hermes.lan>
2019-01-05 0:35 ` Liwu Liu
2019-01-05 1:08 ` Stephen Hemminger
2019-01-08 18:38 ` Liwu Liu [this message]
2019-01-04 22:28 Liwu Liu
2019-01-05 9:45 ` Olga Shern
2019-01-07 17:46 ` Liwu Liu
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=a064008d85da4aeba554252e57dac005@fortinet.com \
--to=liwuliu@fortinet.com \
--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).