Hi folks,
I'm trying to use the flow steering features of the Mellanox card to
effectively use a multicore server for a benchmark.
The system has a single-port Mellanox ConnectX-3 EN, and I want to use 4 of
the 32 cores present and 4 of the 16 RX queues supported by the hardware
(i.e. one RX queu
Currently, the DPDK PMD and NIC kernel driver cannot drive a same NIC device
simultaneously. When you
use ethtool to setup flow director filter, the rules are written to NIC via
ethtool support in kernel driver. But when
DPDK PMD is loaded to drive same device, the rules previously written by
et
On Fri, Apr 10, 2015 at 07:25:32PM +, Wiles, Keith wrote:
>
>
> On 4/9/15, 6:53 AM, "Neil Horman" wrote:
>
> >On Wed, Apr 08, 2015 at 03:58:38PM -0500, Keith Wiles wrote:
> >> Move a number of device specific define, structures and functions
> >> into a generic device base set of files for
Hi Danny,
Thanks, that's helpful. However, Mellanox cards don't support Intel Flow
Director, so how would one go about installing these rules in the NIC? The
only technique the Mellanox User Manual (
http://www.mellanox.com/related-docs/prod_software/Mellanox_EN_for_Linux_User_Manual_v2_0-3_0_0.pd
Hi Raghav,
You are right with your observations, Mellanox PMD and mlx4_en (kernel driver)
are co-exist.
When DPDK application run, all traffic is redirected to DPDK application. When
DPDK application exit the traffic is received by mlx4_en driver.
Regarding ethtool configuration you did, it i
Thanks for clarification Olga. I assume when PMD is upgraded to support flow
director, the rules should be only set
by PMD while DPDK application is running, right? Also, when DPDK application
exits, the rules previously written by
the PMD are invalid then user needs to reset rules by ethtool via
6 matches
Mail list logo
