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@dpdk.org> On Behalf Of users-request@dpdk.org Sent: Sunday, February 17, 2019 3:00 AM To: users@dpdk.org Subject: users Digest, Vol 173, Issue 6 Send users mailing list submissions to users@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@dpdk.org You can reach the person managing the list at users-owner@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@filipjaniszewski.com> To: "users@dpdk.org" <users@dpdk.org> Subject: [dpdk-users] flow rule rejected by device Message-ID: <f74c0851-8350-b230-b906-e66af8835cd1@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@gmail.com> To: Filip Janiszewski <contact@filipjaniszewski.com> Cc: "users@dpdk.org" <users@dpdk.org> Subject: Re: [dpdk-users] flow rule rejected by device Message-ID: <CA+Gp1nbYzBX7JJNfYQ7nX2ZJ6nh-zxpEv5jWu8GQCeE=8TGr9A@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@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@filipjaniszewski.com> To: Cliff Burdick <shaklee3@gmail.com> Cc: "users@dpdk.org" <users@dpdk.org> Subject: Re: [dpdk-users] flow rule rejected by device Message-ID: <0d068419-3931-34ec-493d-c4cd1a2b99b1@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@filipjaniszewski.com <mailto:contact@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. ***