DPDK usage discussions
 help / color / mirror / Atom feed
From: Timur Bogdanov <timurbogdanov@gmail.com>
To: Adrien Mazarguil <adrien.mazarguil@6wind.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: Fri, 19 Jan 2018 14:10:29 +0300	[thread overview]
Message-ID: <CAFSCPKtphwSKtEe=yY_fm8tTKZ4YCEANF27FiHVvPgAq8h-6eA@mail.gmail.com> (raw)
In-Reply-To: <20180118150505.GP4256@6wind.com>

Server kernel is 4.14.13-1.el7.elrepo.x86_64.
The rdma-core is v16.
Parameter "log_num_mgm_entry_size" is set to "-1"
So I don't know why testpmd still runs with same error:

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
/Regards, Timur


On Thu, Jan 18, 2018 at 6:05 PM, Adrien Mazarguil
<adrien.mazarguil@6wind.com> wrote:
> On Thu, Jan 18, 2018 at 03:11:16PM +0300, Timur Bogdanov wrote:
>> Yes, the problem was in this parameter and after changing it to "-1"
>> testpmd application has been started successfully.
>>
>> BUT, it started successfully only on server where Mellanox OFED is installed.
>>
>> On  another server a rdma-core was installed from sources. (rpm's were
>> built and installed)
>> I also changed the value of log_num_mgm_entry_size parameter to "-1"
>> and restarted a server (since where is no openibd service on this
>> server) and got the same error.
>> Maybe mlx4_core kernel module parameter should be changed in some
>> other config file?
>
> In case MLNX_OFED is *not* installed, do both rdma-core and kernel version
> meet the minimum requirements?
>
> - rdma-core v15
> - Linux 4.14
>
> Note while the above versions are fine for mlx5 (ConnectX-4, ConnectX-5),
> they provide reduced performance and RSS capabilities for mlx4 (ConnectX-3),
> for which I recommend to use at least:
>
> - rdma-core v16
> - Linux 4.15 (not released yet, 4.15-rc8 will do in the meantime)
>
>> Anyway, I can also install and use OFED instead of RDMA but the RDMA
>> is pointed as recommended on instructions page
>> "http://dpdk.org/doc/guides/nics/mlx4.html" and it is interesting to
>> bring it to working state.
>> /Regards, Timur
>
> rdma-core requires an up-to-date kernel. If this can't be satisfied,
> MLNX_OFED is the only alternative (the mlnx-ofa_kernel package).
>
>> On Thu, Jan 18, 2018 at 11:48 AM, Adrien Mazarguil
>> <adrien.mazarguil@6wind.com> wrote:
>> > 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
>
> --
> Adrien Mazarguil
> 6WIND

  reply	other threads:[~2018-01-19 11:10 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
2018-01-18 12:11   ` Timur Bogdanov
2018-01-18 15:05     ` Adrien Mazarguil
2018-01-19 11:10       ` Timur Bogdanov [this message]
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='CAFSCPKtphwSKtEe=yY_fm8tTKZ4YCEANF27FiHVvPgAq8h-6eA@mail.gmail.com' \
    --to=timurbogdanov@gmail.com \
    --cc=adrien.mazarguil@6wind.com \
    --cc=olgas@mellanox.com \
    --cc=shahafs@mellanox.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).