DPDK usage discussions
 help / color / mirror / Atom feed
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
Date: Sun, 17 Feb 2019 08:40:20 +0100	[thread overview]
Message-ID: <0d068419-3931-34ec-493d-c4cd1a2b99b1@filipjaniszewski.com> (raw)
In-Reply-To: <CA+Gp1nbYzBX7JJNfYQ7nX2ZJ6nh-zxpEv5jWu8GQCeE=8TGr9A@mail.gmail.com>

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

      reply	other threads:[~2019-02-17  7:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-16 14:19 Filip Janiszewski
2019-02-17  4:32 ` Cliff Burdick
2019-02-17  7:40   ` Filip Janiszewski [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=0d068419-3931-34ec-493d-c4cd1a2b99b1@filipjaniszewski.com \
    --to=contact@filipjaniszewski.com \
    --cc=shaklee3@gmail.com \
    --cc=users@dpdk.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).