Hi Everyone,
I am using X722 NIC with DPDK 19.11 after a single line patch for port
detection as was advised earlier.
The port gets detected properly.
The NIC stats via rte_eth_stats_get report that the packets are arriving at
NIC. There are no packets that are dropped due to no-mbuf's
But the
On 3/26/2020 12:00, Benoit Ganne (bganne) wrote:
>> Pasting back this important info:
>> "
>> Note that ethtool and '/sys/class/net//speed' also fails
>> to report the link speed (but not the link status).
>> "
>>
>> 26/03/2020 19:27, Benoit Ganne (bganne):
>>> Yes everything is initialized
On 3/26/2020 12:00, Benoit Ganne (bganne) wrote:
> Just removing the over-strict check in mlx5 PMD is enough for everything to
> work fine:
> https://gerrit.fd.io/r/c/vpp/+/26152/1/build/external/patches/dpdk_20.02/0002-mlx5-azure-workaround.patch
[...]
> 2) mlx5 PMD enforce that both link speed
06/03/2020 01:45, Liwu Liu:
> Hi Team,
>
> I am using the mlx5/100G in KVM guest. The host shows this PCI vfNIC is
> provisioned to the guest:
> "17:01.1 Ethernet controller: Mellanox Technologies MT27800 Family
> [ConnectX-5 Virtual Function]"
>
> I am using DPDK 19.11 with kind of
Hi,
Sorry for the late answer.
22/10/2019 10:38, guyifan:
> DPDK version 18.11.2，imiss is always 0.
> And I could not find any code about 'imiss' in
> 'dpdk-stable-18.11.2/drivers/net/mlx5/' or
> 'dpdk-stable-18.11.2/drivers/net/mlx4/'.
> Is there any way to know how many packets have been
Thanks for the interesting feedback.
It seems we should test this performance use case in our labs.
18/02/2020 09:36, Hrvoje Habjanic:
> On 08. 04. 2019. 11:52, Hrvoje Habjanić wrote:
> > On 29/03/2019 08:24, Hrvoje Habjanić wrote:
> >>> Hi.
> >>>
> >>> I did write an application using dpdk
26/03/2020 21:09, Mark Bloch:
>
> On 3/26/2020 12:00, Benoit Ganne (bganne) wrote:
> >> Pasting back this important info:
> >> "
> >> Note that ethtool and '/sys/class/net//speed' also fails
> >> to report the link speed (but not the link status).
> >> "
> >>
> >> 26/03/2020 19:27, Benoit Ganne
> Pasting back this important info:
> "
> Note that ethtool and '/sys/class/net//speed' also fails
> to report the link speed (but not the link status).
> "
>
> 26/03/2020 19:27, Benoit Ganne (bganne):
> > Yes everything is initialized correctly. The netdev itself is configured
> and usable from
> Is the Mellanox device being brought up by the base kernel setup?
> I find that for Mellanox the device has to be started from kernel (like
> ip) and DPDK doesn't do itself.
Yes everything is initialized correctly. The netdev itself is configured and
usable from Linux (ping etc.). Just
On Thu, 26 Mar 2020 14:26:56 +
"Benoit Ganne (bganne)" wrote:
> Hi Stephen,
>
> > Is this with netvsc PMD or failsafe PMD?
>
> I am using failsafe PMD using the string "--vdev net_vdev_netvsc0,iface=eth1"
> etc. as mentioned here:
>
Hi Stephen,
> Is this with netvsc PMD or failsafe PMD?
I am using failsafe PMD using the string "--vdev net_vdev_netvsc0,iface=eth1"
etc. as mentioned here:
https://docs.microsoft.com/en-us/azure/virtual-network/setup-dpdk
I checked with gdb what are the underlying devices and there is 1 mlx5
11 matches
Mail list logo
