DPDK usage discussions
 help / color / mirror / Atom feed
From: Adrien Mazarguil <adrien.mazarguil@6wind.com>
To: Timur Bogdanov <timurbogdanov@gmail.com>
Cc: users@dpdk.org, Olga Shern <olgas@mellanox.com>,
	Shahaf Shuler <shahafs@mellanox.com>,
	Timothy Redaelli <tredaelli@redhat.com>
Subject: Re: [dpdk-users] Unable to launch testpmd with Mellanox ConnectX-3 Pro NIC
Date: Thu, 18 Jan 2018 09:48:28 +0100	[thread overview]
Message-ID: <20180118084828.GO4256@6wind.com> (raw)
In-Reply-To: <CAFSCPKuV_nRi3X3n+Z0stEKNA91w2-YgcZ62O3-T79dHXT-mUQ@mail.gmail.com>

On Tue, Jan 16, 2018 at 06:59:31PM +0300, Timur Bogdanov wrote:
> Hi,
> 
> I'm trying to use dpdk with Mellanox ConnectX-3 Pro NIC.
> I built PMD for it according to instructions on
> "http://dpdk.org/doc/guides/nics/mlx4.html" and tried to launch
> testpmd app but got following error:
<snip>
> PMD: net_mlx4: 0xda13c0: cannot attach flow rules (code 95, "Operation
> not supported"), flow error type 2, cause 0x7f2869cdab80, message:
> flow rule rejected by device
> 
> Fail to start port 0
<snip>
> What can be the reason of testpmd does not start correctly?

Did you provide by any chance -7 instead of -1 as a value for mlx4_core.ko's
log_num_mgm_entry_size parameter (as recommended by the above
documentation)?

Timothy (CC'ed) reported that -7 does not quite work with the default flow
rules (too many limitations) and results in the above error message. -1
should be used, -7 is only for specific use cases and should probably not
even be documented in this file.

-- 
Adrien Mazarguil
6WIND

  reply	other threads:[~2018-01-18  8:48 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-16 15:59 Timur Bogdanov
2018-01-18  8:48 ` Adrien Mazarguil [this message]
2018-01-18 12:11   ` Timur Bogdanov
2018-01-18 15:05     ` Adrien Mazarguil
2018-01-19 11:10       ` Timur Bogdanov
2018-01-20 19:10         ` Timur Bogdanov

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=20180118084828.GO4256@6wind.com \
    --to=adrien.mazarguil@6wind.com \
    --cc=olgas@mellanox.com \
    --cc=shahafs@mellanox.com \
    --cc=timurbogdanov@gmail.com \
    --cc=tredaelli@redhat.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).