From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp.fortinet.com (smtp.fortinet.com [208.91.113.81]) by dpdk.org (Postfix) with ESMTP id 07E2A58C6 for ; Tue, 19 Feb 2019 18:29:47 +0100 (CET) Received: from mail.fortinet.com ([192.168.221.134]) by smtp.fortinet.com with ESMTP id x1JHTkTs016854-x1JHTkTu016854 (version=TLSv1.2 cipher=AES256-SHA256 bits=256 verify=FAIL) for ; Tue, 19 Feb 2019 09:29:47 -0800 Received: from FGT-EXCH-MBX132.fortinet-us.com (192.168.221.132) by FGT-EXCH-MBX134.fortinet-us.com (192.168.221.134) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.1531.3; Tue, 19 Feb 2019 09:29:46 -0800 Received: from FGT-EXCH-MBX132.fortinet-us.com ([fe80::78b9:5f97:8cec:b419]) by FGT-EXCH-MBX132.fortinet-us.com ([fe80::78b9:5f97:8cec:b419%10]) with mapi id 15.01.1531.003; Tue, 19 Feb 2019 09:29:46 -0800 From: Liwu Liu To: "users@dpdk.org" Thread-Topic: users Digest, Vol 173, Issue 6 Thread-Index: AQHUxq/xawCDzEil7E+sLow4Y7JrpaXnZHWA Date: Tue, 19 Feb 2019 17:29:46 +0000 Message-ID: References: In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [96.45.36.15] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; d=fortinet.com; s=dkim; c=relaxed/relaxed; h=from:to:subject:date:message-id:references:content-type:mime-version; bh=SBhlNfXnWyS5YpnpGtDUoufqi3vMmYCHaajH9/OWtQc=; b=SMhnMSeMUdW2CXpoe9m+aZnaPNoX5xtORqdDi6To2mzM+BhC1ZdCjyGSdRCzRBuC6zQRRKtGXndB CgC++GISMayFIlPWZ58eNGm657gvI1Dz9qrmGzQuGFpRg12Y9khp7it36aQuEkJD4IxunMuFfIDJ WY89sarEGpysEuWY0bKSPkXb/u782VnJ0IkQQ2/s5R/Pf7pesg+YWlkwfnCQ4Ey9wBElDmdJI3j6 t2uXtRki6ZU6+CJNRs5NOLh4awYE9RuwRgnVKAlWDa8ey8tBk2qc6yYSv0ihRBM3NJ7lZnKOJizs xs9/Fzvsls+Vd0SERUWPWbVO8bRXPvYOupQ6+w== Subject: Re: [dpdk-users] users Digest, Vol 173, Issue 6 X-BeenThere: users@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK usage discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 19 Feb 2019 17:29:48 -0000 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 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 To: "users@dpdk.org" Subject: [dpdk-users] flow rule rejected by device Message-ID: Content-Type: text/plain; charset=3Diso-8859-15 Hi All, I have a weird issue with an re-branded Mellanox card (sold as HP, but ML= X 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 no= t supported"), flow error type 2, cause 0x7f76cd22b680, message: flow rul= e 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 re= quired 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 ca= n 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 To: Filip Janiszewski Cc: "users@dpdk.org" Subject: Re: [dpdk-users] flow rule rejected by device Message-ID: Content-Type: text/plain; charset=3D"UTF-8" What type are flow are you creating? I believe #95 is simply that it's no= t 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 thos= e > 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 wit= h > 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_Star= t_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 To: Cliff Burdick Cc: "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=3Dutf-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 wil= l > support different flows, but it should be traceable in the driver. > > On Sat, Feb 16, 2019 at 6:20 AM Filip Janiszewski > > wr= ote: > > 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, "Operat= ion > 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 vers= ion > 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 firmw= are > 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 confid= ential and proprietary material and information and are intended only for= the use of the intended recipient(s). If you are not the intended recipi= ent, you are hereby notified that any review, use, disclosure, disseminat= ion, distribution or copying of this message and any attachments is stric= tly prohibited. If you have received this email in error, please immediat= ely 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 Fort= inet, Inc., its affiliates, and emails are not binding on Fortinet and on= ly a writing manually signed by Fortinet's General Counsel can be a bindi= ng commitment of Fortinet to Fortinet's customers or partners. Thank you.= ***