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? 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 On Thu, Jan 18, 2018 at 11:48 AM, Adrien Mazarguil <adrien.mazarg...@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