[dpdk-users] NIC Compatibility

puneet_kumar kumar puneet_kumar_kumar at yahoo.com
Fri Feb 22 11:44:15 CET 2019


Hi Everyone,
I have a Dell R720 Server and it has embedded NICs 5700 Broadcom family. I checked supported NiC for DPDK in http://doc.dpdk.org/guides/nics/bnxt.html and found out that support is for BCM5730X / BCM574XX / BCM58000 family of Ethernet Network Controllers. Can someone please suggest a NIC for DPDK purpose which can also be plugged into R720 Dell Server.
Help is highly appreciated! 
Best regards,Puneet 

    On Wednesday, 20 February, 2019, 3:00:06 am GMT-8, <users-request at dpdk.org> wrote:  
 
 Send users mailing list submissions to
    users at dpdk.org

To subscribe or unsubscribe via the World Wide Web, visit
    https://mails.dpdk.org/listinfo/users
or, via email, send a message with subject or body 'help' to
    users-request at dpdk.org

You can reach the person managing the list at
    users-owner at dpdk.org

When replying, please edit your Subject line so it is more specific
than "Re: Contents of users digest..."


Today's Topics:

  1. Re: users Digest, Vol 173, Issue 6 (Liwu Liu)


----------------------------------------------------------------------

Message: 1
Date: Tue, 19 Feb 2019 17:29:46 +0000
From: Liwu Liu <liwuliu at fortinet.com>
To: "users at dpdk.org" <users at dpdk.org>
Subject: Re: [dpdk-users] users Digest, Vol 173, Issue 6
Message-ID: <ae326aff264f4a47b68bca7b0d8191c0 at fortinet.com>
Content-Type: text/plain; charset="us-ascii"

I think you have to define certain flow rules into NIC to let it forward traffic to your DPDK user-land CQ.
The hardware flow rule is used for the NIC to determine which packets to forward to DPDK rxq. 
No flow rule, receive no packet.

-----Original Message-----
From: users <users-bounces at dpdk.org> On Behalf Of users-request at dpdk.org
Sent: Sunday, February 17, 2019 3:00 AM
To: users at dpdk.org
Subject: users Digest, Vol 173, Issue 6

Send users mailing list submissions to
    users at dpdk.org

To subscribe or unsubscribe via the World Wide Web, visit
    https://mails.dpdk.org/listinfo/users
or, via email, send a message with subject or body 'help' to
    users-request at dpdk.org

You can reach the person managing the list at
    users-owner at dpdk.org

When replying, please edit your Subject line so it is more specific than "Re: Contents of users digest..."


Today's Topics:

  1. flow rule rejected by device (Filip Janiszewski)
  2. Re: flow rule rejected by device (Cliff Burdick)
  3. Re: flow rule rejected by device (Filip Janiszewski)


----------------------------------------------------------------------

Message: 1
Date: Sat, 16 Feb 2019 15:19:59 +0100
From: Filip Janiszewski <contact at filipjaniszewski.com>
To: "users at dpdk.org" <users at dpdk.org>
Subject: [dpdk-users] flow rule rejected by device
Message-ID:
    <f74c0851-8350-b230-b906-e66af8835cd1 at filipjaniszewski.com>
Content-Type: text/plain; charset=iso-8859-15

Hi All,

I have a weird issue with an re-branded Mellanox card (sold as HP, but MLX hardware: HP InfiniBand FDR/EN 10/40Gb Dual Port 544FLR-QSFP
Adapter) which is failing to start (rte_eth_dev_start) with the following message:

.
PMD: net_mlx4: 0xebbf40: cannot attach flow rules (code 95, "Operation not supported"), flow error type 2, cause 0x7f76cd22b680, message: flow rule rejected by device .

I can't say what that cause means, any suggestion on how to decode those numbers? Also, I don't have configured any flow rule (or nothing
related) and the very same code works fine one a ConnectX-4 Lx.

I suspect a firmware compatibility issue, as the HP card is running with the FW version 2.30.3200 while apparently the Minimum firmware version required to support DPDK is 2.36.5000:

http://www.mellanox.com/related-docs/prod_software/MLNX_DPDK_Quick_Start_Guide_v16.11_1.5.pdf

(Page 8).

The HP card is running on Mellanox firmware.

Did anyone encountered a similar issue and can comment if the firmware can be the problem here?

Thanks

--
BR, Filip
+48 666 369 823


------------------------------

Message: 2
Date: Sat, 16 Feb 2019 20:32:57 -0800
From: Cliff Burdick <shaklee3 at gmail.com>
To: Filip Janiszewski <contact at filipjaniszewski.com>
Cc: "users at dpdk.org" <users at dpdk.org>
Subject: Re: [dpdk-users] flow rule rejected by device
Message-ID:
    <CA+Gp1nbYzBX7JJNfYQ7nX2ZJ6nh-zxpEv5jWu8GQCeE=8TGr9A at mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"

What type are flow are you creating? I believe #95 is simply that it's not
supported on that NIC. I'm not sure if an HP variant of the CX4 will
support different flows, but it should be traceable in the driver.

On Sat, Feb 16, 2019 at 6:20 AM Filip Janiszewski <
contact at filipjaniszewski.com> wrote:

> Hi All,
>
> I have a weird issue with an re-branded Mellanox card (sold as HP, but
> MLX hardware: HP InfiniBand FDR/EN 10/40Gb Dual Port 544FLR-QSFP
> Adapter) which is failing to start (rte_eth_dev_start) with the
> following message:
>
> .
> PMD: net_mlx4: 0xebbf40: cannot attach flow rules (code 95, "Operation
> not supported"), flow error type 2, cause 0x7f76cd22b680, message: flow
> rule rejected by device
> .
>
> I can't say what that cause means, any suggestion on how to decode those
> numbers? Also, I don't have configured any flow rule (or nothing
> related) and the very same code works fine one a ConnectX-4 Lx.
>
> I suspect a firmware compatibility issue, as the HP card is running with
> the FW version 2.30.3200 while apparently the Minimum firmware version
> required to support DPDK is 2.36.5000:
>
>
> http://www.mellanox.com/related-docs/prod_software/MLNX_DPDK_Quick_Start_Guide_v16.11_1.5.pdf
>
> (Page 8).
>
> The HP card is running on Mellanox firmware.
>
> Did anyone encountered a similar issue and can comment if the firmware
> can be the problem here?
>
> Thanks
>
> --
> BR, Filip
> +48 666 369 823
>


------------------------------

Message: 3
Date: Sun, 17 Feb 2019 08:40:20 +0100
From: Filip Janiszewski <contact at filipjaniszewski.com>
To: Cliff Burdick <shaklee3 at gmail.com>
Cc: "users at dpdk.org" <users at dpdk.org>
Subject: Re: [dpdk-users] flow rule rejected by device
Message-ID:
    <0d068419-3931-34ec-493d-c4cd1a2b99b1 at filipjaniszewski.com>
Content-Type: text/plain; charset=utf-8

I'm not creating any flow at all, that's the weird part.

Il 17/02/19 05:32, Cliff Burdick ha scritto:
> What type are flow are you creating? I believe #95 is simply that it's
> not supported on that NIC. I'm not sure if an HP variant of the CX4 will
> support different flows, but it should be traceable in the driver.
> 
> On Sat, Feb 16, 2019 at 6:20 AM Filip Janiszewski
> <contact at filipjaniszewski.com <mailto:contact at filipjaniszewski.com>> wrote:
> 
>    Hi All,
> 
>    I have a weird issue with an re-branded Mellanox card (sold as HP, but
>    MLX hardware: HP InfiniBand FDR/EN 10/40Gb Dual Port 544FLR-QSFP
>    Adapter) which is failing to start (rte_eth_dev_start) with the
>    following message:
> 
>    .
>    PMD: net_mlx4: 0xebbf40: cannot attach flow rules (code 95, "Operation
>    not supported"), flow error type 2, cause 0x7f76cd22b680, message: flow
>    rule rejected by device
>    .
> 
>    I can't say what that cause means, any suggestion on how to decode those
>    numbers? Also, I don't have configured any flow rule (or nothing
>    related) and the very same code works fine one a ConnectX-4 Lx.
> 
>    I suspect a firmware compatibility issue, as the HP card is running with
>    the FW version 2.30.3200 while apparently the Minimum firmware version
>    required to support DPDK is 2.36.5000:
> 
>    http://www.mellanox.com/related-docs/prod_software/MLNX_DPDK_Quick_Start_Guide_v16.11_1.5.pdf
> 
>    (Page 8).
> 
>    The HP card is running on Mellanox firmware.
> 
>    Did anyone encountered a similar issue and can comment if the firmware
>    can be the problem here?
> 
>    Thanks
> 
>    -- 
>    BR, Filip
>    +48 666 369 823
> 

-- 
BR, Filip
+48 666 369 823


End of users Digest, Vol 173, Issue 6
*************************************


***  Please note that this message and any attachments may contain confidential and proprietary material and information and are intended only for the use of the intended recipient(s). If you are not the intended recipient, you are hereby notified that any review, use, disclosure, dissemination, distribution or copying of this message and any attachments is strictly prohibited. If you have received this email in error, please immediately notify the sender and destroy this e-mail and any attachments and all copies, whether electronic or printed. Please also note that any views, opinions, conclusions or commitments expressed in this message are those of the individual sender and do not necessarily reflect the views of Fortinet, Inc., its affiliates, and emails are not binding on Fortinet and only a writing manually signed by Fortinet's General Counsel can be a binding commitment of Fortinet to Fortinet's customers or partners. Thank you. *** 




End of users Digest, Vol 174, Issue 1
*************************************
  


More information about the users mailing list