Re: [ovs-discuss] [Ryu-devel] Meter Table Support in Openvswitch

2018-02-20 Thread Iwase Yusuke 

Hi Suresh and Thanks Yi!

FYI, Ryu provides "OpenFlow Switch Test Tool" for testing whether your switch
support the features of OpenFlow including the Meter.
This tool is one of the built-in application of Ryu and easy to start using.
http://osrg.github.io/ryu-book/en/html/switch_test_tool.html

Thanks,
Iwase

On 2018年02月20日 13:32, Yi Tseng wrote:

[c.c. to ovs mailing list]

2018-02-18 23:10 GMT-08:00 knet solutions >:


Hi,

Does OpenVSwitch(latest release 2.8.1 + )  support Meter table?
In the release notes, its mentioned  2.7.0 onward its supported.  Is it 
correct?

Thanks
Suresh


--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
Ryu-devel mailing list
ryu-de...@lists.sourceforge.net 
https://lists.sourceforge.net/lists/listinfo/ryu-devel





--
Yi Tseng (a.k.a Takeshi)
Taiwan National Chiao Tung University
Department of Computer Science
W2CNLab

https://takeshi.tw


___
discuss mailing list
disc...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-discuss


___
discuss mailing list
disc...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-discuss

[ovs-discuss] Open vSwitch 2.9.0 and 2.8.2 Available

2018-02-20 Thread Justin Pettit 
The Open vSwitch team is pleased to announce the release of Open vSwitch 2.9.0:

 http://openvswitch.org/releases/openvswitch-2.9.0.tar.gz

A few other feature highlights of 2.9.0 include:

 - No longer slow-path traffic that is sent to a controller.

 - The DPDK version of OVS adds support for DPDK v17.11 and vHost IOMMU.

 - OVN adds support to send IPv6 Router Advertisement packets in response to
   the IPv6 Router Solicitation packets from VIF ports.

 - NSH support in the Linux kernel datapath.

 - Support for Linux kernels up to 4.13.

 - And many others.  See the full change log here:

 http://openvswitch.org/releases/NEWS-2.9.0

In addition to the 2.9.0 release, we've also released 2.8.2:

 http://openvswitch.org/releases/openvswitch-2.8.2.tar.gz

This release contains bug fixes for 2.8.1 as well as updating NSH support to 
the latest IETF draft.

We plan to release 2.9.1 in the near future that will add support for clustered 
OVSDB using the Raft consensus algorithm.  This will be particularly useful for 
OVN, since it will allow multiple instances of the database to be run to 
provide better performance and reliability.

Enjoy!

--The Open vSwitch Team   

   
Open vSwitch is a production quality, multilayer open source virtual switch. It 
is designed to enable massive network automation through programmatic 
extension, while still supporting standard management interfaces. Open vSwitch 
can operate both as a soft switch running within the hypervisor, and as the 
control stack for switching silicon. It has been ported to multiple 
virtualization platforms and switching chipsets.


___
discuss mailing list
disc...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-discuss

Re: [ovs-discuss] OpenStack profiling with networking-ovn - port creation is slow

2018-02-20 Thread Daniel Alvarez 



> On 20 Feb 2018, at 19:50, Lucas Alvares Gomes  wrote:
> 
> Hi,
> 
>> On Tue, Feb 20, 2018 at 4:56 PM, Han Zhou  wrote:
>> 
>> 
>>> On Tue, Feb 20, 2018 at 8:15 AM, Ben Pfaff  wrote:
>>> 
 On Mon, Feb 19, 2018 at 11:33:11AM +0100, Daniel Alvarez Sanchez wrote:
 @Han, I can try rebase the patch if you want but that was
 basically renaming the Address_Set table and from Ben's
 comment, it may be better to keep the name. Not sure,
 however, how we can proceed to address Lucas' points in
 this thread.
>>> 
>>> I wouldn't rename the table.  It sounds like the priority should be to
>>> add support for sets of port names.  I thought that there was already a
>>> patch for that to be rebased, but maybe I misunderstood.
>> 
>> I feel it is better to add a new table for port group explicitly, and the
>> column type can be a set of weak reference to Logical_Switch_Port.
>> The benefits are:
>> - Better data integrity: deleting a lport automatically deletes from the
>> port group
>> - No confusion about the type of records in a single table
>> - Existing Address_Set mechanism will continue to be supported without any
>> change
>> - Furthermore, the race condition issue brought up by Lucas can be solved by
>> supporting port-group in IP address match condition in ovn-controller, so
>> that all addresses in the lports are used just like how AddressSet is used
>> today. And there is no need for Neutron networking-ovn to use AddressSet any
>> more. Since addresses are deduced from lports, the ordering of
>> deleting/adding doesn't matter any more.
>> 
>> How does this sound?

+1 from me too! Even though I understand the reasons brought up by Ben I think 
this might be the right plan forward! We can try to work on it together Han.
Thanks a lot guys.
Daniel 
>> 
> 
> +1 from me, I quite like it! It would solve both problems raised in
> this thread and won't break any existing code.
> 
> (Also, thanks for all the previous suggestions @Ben, @Han and @Daniel.
> This thread has been really helpful!)
> 
> Cheers,
> Lucas
> ___
> discuss mailing list
> disc...@openvswitch.org
> https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
___
discuss mailing list
disc...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-discuss

Re: [ovs-discuss] OpenStack profiling with networking-ovn - port creation is slow

2018-02-20 Thread Lucas Alvares Gomes 
Hi,

On Tue, Feb 20, 2018 at 4:56 PM, Han Zhou  wrote:
>
>
> On Tue, Feb 20, 2018 at 8:15 AM, Ben Pfaff  wrote:
>>
>> On Mon, Feb 19, 2018 at 11:33:11AM +0100, Daniel Alvarez Sanchez wrote:
>> > @Han, I can try rebase the patch if you want but that was
>> > basically renaming the Address_Set table and from Ben's
>> > comment, it may be better to keep the name. Not sure,
>> > however, how we can proceed to address Lucas' points in
>> > this thread.
>>
>> I wouldn't rename the table.  It sounds like the priority should be to
>> add support for sets of port names.  I thought that there was already a
>> patch for that to be rebased, but maybe I misunderstood.
>
> I feel it is better to add a new table for port group explicitly, and the
> column type can be a set of weak reference to Logical_Switch_Port.
> The benefits are:
> - Better data integrity: deleting a lport automatically deletes from the
> port group
> - No confusion about the type of records in a single table
> - Existing Address_Set mechanism will continue to be supported without any
> change
> - Furthermore, the race condition issue brought up by Lucas can be solved by
> supporting port-group in IP address match condition in ovn-controller, so
> that all addresses in the lports are used just like how AddressSet is used
> today. And there is no need for Neutron networking-ovn to use AddressSet any
> more. Since addresses are deduced from lports, the ordering of
> deleting/adding doesn't matter any more.
>
> How does this sound?
>

+1 from me, I quite like it! It would solve both problems raised in
this thread and won't break any existing code.

(Also, thanks for all the previous suggestions @Ben, @Han and @Daniel.
This thread has been really helpful!)

Cheers,
Lucas
___
discuss mailing list
disc...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-discuss

Re: [ovs-discuss] OvS build (w DPDK) failed - Undefined Mellanox references

2018-02-20 Thread Olga Shern 
How do you compile OVS?

-Original Message-
From: Avi Cohen (A) [mailto:avi.co...@huawei.com] 
Sent: Tuesday, February 20, 2018 1:39 PM
To: Olga Shern ; ovs-discuss@openvswitch.org
Cc: Erez Ferber 
Subject: RE: [ovs-discuss] OvS build (w DPDK) failed - Undefined Mellanox 
references

Thank you Olga

Now dpdk build is ok but ovs build fail because of ibv* undefined reference



/home/avi/dpdk-stable-17.05.2/x86_64-native-linuxapp-gcc/lib/librte_pmd_mlx5.a(mlx5.o):
 In function `mlx5_dev_close':
/home/avi/dpdk-stable-17.05.2/drivers/net/mlx5/mlx5.c:195: undefined reference 
to `ibv_dealloc_pd'
/home/avi/dpdk-stable-17.05.2/drivers/net/mlx5/mlx5.c:196: undefined reference 
to `ibv_close_device'
/home/avi/dpdk-stable-17.05.2/x86_64-native-linuxapp-gcc/lib/librte_pmd_mlx5.a(mlx5.o):
 In function `mlx5_pci_probe':
/home/avi/dpdk-stable-17.05.2/drivers/net/mlx5/mlx5.c:453: undefined reference 
to `ibv_get_device_list'
/home/avi/dpdk-stable-17.05.2/drivers/net/mlx5/mlx5.c:513: undefined reference 
to `ibv_open_device'
/home/avi/dpdk-stable-17.05.2/drivers/net/mlx5/mlx5.c:533: undefined reference 
to `ibv_query_device'
/home/avi/dpdk-stable-17.05.2/drivers/net/mlx5/mlx5.c:829: undefined reference 
to `ibv_close_device'
/home/avi/dpdk-stable-17.05.2/drivers/net/mlx5/mlx5.c:831: undefined reference 
to `ibv_free_device_list'
/home/avi/dpdk-stable-17.05.2/drivers/net/mlx5/mlx5.c:518: undefined reference 
to `ibv_free_device_list'
/home/avi/dpdk-stable-17.05.2/drivers/net/mlx5/mlx5.c:568: undefined reference 
to `ibv_open_device'
/home/avi/dpdk-stable-17.05.2/x86_64-native-linuxapp-gcc/lib/librte_pmd_mlx5.a(mlx5.o):
 In function `___ibv_query_port':
/usr/include/infiniband/verbs.h:1227: undefined reference to `ibv_query_port'
/home/avi/dpdk-stable-17.05.2/x86_64-native-linuxapp-gcc/lib/librte_pmd_mlx5.a(mlx5.o):
 In function `mlx5_pci_probe':
/home/avi/dpdk-stable-17.05.2/drivers/net/mlx5/mlx5.c:591: undefined reference 
to `ibv_alloc_pd'
/home/avi/dpdk-stable-17.05.2/drivers/net/mlx5/mlx5.c:808: undefined reference 
to `ibv_dealloc_pd'
/home/avi/dpdk-stable-17.05.2/drivers/net/mlx5/mlx5.c:810: undefined reference 
to `ibv_close_device'
/home/avi/dpdk-stable-17.05.2/drivers/net/mlx5/mlx5.c:749: undefined reference 
to `ibv_get_device_name'
/home/avi/dpdk-stable-17.05.2/drivers/net/mlx5/mlx5.c:518: undefined reference 
to `ibv_free_device_list'
/home/avi/dpdk-stable-17.05.2/x86_64-native-linuxapp-gcc/lib/librte_pmd_mlx5.a(mlx5.o):
 In function `rte_mlx5_pmd_init':
/home/avi/dpdk-stable-17.05.2/drivers/net/mlx5/mlx5.c:897: undefined reference 
to `ibv_fork_init'
/home/avi/dpdk-stable-17.05.2/x86_64-native-linuxapp-gcc/lib/librte_pmd_mlx5.a(mlx5_rxq.o):
 In function `priv_create_hash_rxqs':
/home/avi/dpdk-stable-17.05.2/drivers/net/mlx5/mlx5_rxq.c:499: undefined 
reference to `ibv_destroy_qp'
/home/avi/dpdk-stable-17.05.2/x86_64-native-linuxapp-gcc/lib/librte_pmd_mlx5.a(mlx5_rxq.o):
 In function `priv_destroy_hash_rxqs':
/home/avi/dpdk-stable-17.05.2/drivers/net/mlx5/mlx5_rxq.c:549: undefined 
reference to `ibv_destroy_qp'
/home/avi/dpdk-stable-17.05.2/x86_64-native-linuxapp-gcc/lib/librte_pmd_mlx5.a(mlx5_rxq.o):
 In function `rxq_cleanup':
/home/avi/dpdk-stable-17.05.2/drivers/net/mlx5/mlx5_rxq.c:754: undefined 
reference to `ibv_destroy_cq'
/home/avi/dpdk-stable-17.05.2/drivers/net/mlx5/mlx5_rxq.c:756: undefined 
reference to `ibv_destroy_comp_channel'
/home/avi/dpdk-stable-17.05.2/drivers/net/mlx5/mlx5_rxq.c:758: undefined 
reference to `ibv_dereg_mr'
/home/avi/dpdk-stable-17.05.2/x86_64-native-linuxapp-gcc/lib/librte_pmd_mlx5.a(mlx5_rxq.o):
 In function `rxq_ctrl_setup':
/home/avi/dpdk-stable-17.05.2/drivers/net/mlx5/mlx5_rxq.c:979: undefined 
reference to `ibv_create_comp_channel'
/home/avi/dpdk-stable-17.05.2/x86_64-native-linuxapp-gcc/lib/librte_pmd_mlx5.a(mlx5_rxq.o):
 In function `mlx5_rx_intr_disable':
/home/avi/dpdk-stable-17.05.2/drivers/net/mlx5/mlx5_rxq.c:1456: undefined 
reference to `ibv_get_cq_event'
/home/avi/dpdk-stable-17.05.2/drivers/net/mlx5/mlx5_rxq.c:1464: undefined 
reference to `ibv_ack_cq_events'
/home/avi/dpdk-stable-17.05.2/x86_64-native-linuxapp-gcc/lib/librte_pmd_mlx5.a(mlx5_txq.o):
 In function `txq_cleanup':
/home/avi/dpdk-stable-17.05.2/drivers/net/mlx5/mlx5_txq.c:148: undefined 
reference to `ibv_destroy_qp'
/home/avi/dpdk-stable-17.05.2/drivers/net/mlx5/mlx5_txq.c:150: undefined 
reference to `ibv_destroy_cq'
/home/avi/dpdk-stable-17.05.2/drivers/net/mlx5/mlx5_txq.c:155: undefined 
reference to `ibv_dereg_mr'
/home/avi/dpdk-stable-17.05.2/x86_64-native-linuxapp-gcc/lib/librte_pmd_mlx5.a(mlx5_txq.o):
 In function `ibv_exp_create_qp':
/usr/include/infiniband/verbs_exp.h:3009: undefined reference to `ibv_create_qp'
/home/avi/dpdk-stable-17.05.2/x86_64-native-linuxapp-gcc/lib/librte_pmd_mlx5.a(mlx5_ethdev.o):
 In function `priv_dev_link_status_handler':
/home/avi/dpdk-stable-17.05.2/drivers/net/mlx5/mlx5_ethdev.c:1240: undefined 
reference to `ibv_ack_async_event'
/home/avi/dpdk-sta

Re: [ovs-discuss] OpenStack profiling with networking-ovn - port creation is slow

2018-02-20 Thread Han Zhou 
On Tue, Feb 20, 2018 at 8:15 AM, Ben Pfaff  wrote:
>
> On Mon, Feb 19, 2018 at 11:33:11AM +0100, Daniel Alvarez Sanchez wrote:
> > @Han, I can try rebase the patch if you want but that was
> > basically renaming the Address_Set table and from Ben's
> > comment, it may be better to keep the name. Not sure,
> > however, how we can proceed to address Lucas' points in
> > this thread.
>
> I wouldn't rename the table.  It sounds like the priority should be to
> add support for sets of port names.  I thought that there was already a
> patch for that to be rebased, but maybe I misunderstood.

I feel it is better to add a new table for port group explicitly, and the
column type can be a set of weak reference to Logical_Switch_Port.
The benefits are:
- Better data integrity: deleting a lport automatically deletes from the
port group
- No confusion about the type of records in a single table
- Existing Address_Set mechanism will continue to be supported without any
change
- Furthermore, the race condition issue brought up by Lucas can be solved
by supporting port-group in IP address match condition in ovn-controller,
so that all addresses in the lports are used just like how AddressSet is
used today. And there is no need for Neutron networking-ovn to use
AddressSet any more. Since addresses are deduced from lports, the ordering
of deleting/adding doesn't matter any more.

How does this sound?

Thanks,
Han
___
discuss mailing list
disc...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-discuss

Re: [ovs-discuss] OpenStack profiling with networking-ovn - port creation is slow

2018-02-20 Thread Ben Pfaff 
On Mon, Feb 19, 2018 at 11:33:11AM +0100, Daniel Alvarez Sanchez wrote:
> @Han, I can try rebase the patch if you want but that was
> basically renaming the Address_Set table and from Ben's
> comment, it may be better to keep the name. Not sure,
> however, how we can proceed to address Lucas' points in
> this thread.

I wouldn't rename the table.  It sounds like the priority should be to
add support for sets of port names.  I thought that there was already a
patch for that to be rebased, but maybe I misunderstood.
___
discuss mailing list
disc...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-discuss

Re: [ovs-discuss] OVS doesn't apply action in packet_out message

2018-02-20 Thread Ben Pfaff 
On Mon, Feb 19, 2018 at 06:31:20PM -0500, S hj wrote:
> I have some OVSs connected to ONOS controller.
> OVS1---OVS2OVS3
> 
> when OVS1 wants to send packets to OVS3, OVS2 sends packet_in messages to
> the controller including ARP message and ONOS sends packet_out messages
> contain OFPP_FLOOD as an action.
> 
> However, OVS2 doesn't flood the flow toward the OVS3.
> Is there any way to find out why OVS2 by receiving the packet_out,
> doesn't apply the action on the flow?

You could use "ofproto/trace-packet-out" as described in
ovs-vswitchd(8).
___
discuss mailing list
disc...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-discuss

Re: [ovs-discuss] OvS build (w DPDK) failed - Undefined Mellanox references

2018-02-20 Thread Avi Cohen (A) 
Thank you Olga

Now dpdk build is ok but ovs build fail because of ibv* undefined reference



/home/avi/dpdk-stable-17.05.2/x86_64-native-linuxapp-gcc/lib/librte_pmd_mlx5.a(mlx5.o):
 In function `mlx5_dev_close':
/home/avi/dpdk-stable-17.05.2/drivers/net/mlx5/mlx5.c:195: undefined reference 
to `ibv_dealloc_pd'
/home/avi/dpdk-stable-17.05.2/drivers/net/mlx5/mlx5.c:196: undefined reference 
to `ibv_close_device'
/home/avi/dpdk-stable-17.05.2/x86_64-native-linuxapp-gcc/lib/librte_pmd_mlx5.a(mlx5.o):
 In function `mlx5_pci_probe':
/home/avi/dpdk-stable-17.05.2/drivers/net/mlx5/mlx5.c:453: undefined reference 
to `ibv_get_device_list'
/home/avi/dpdk-stable-17.05.2/drivers/net/mlx5/mlx5.c:513: undefined reference 
to `ibv_open_device'
/home/avi/dpdk-stable-17.05.2/drivers/net/mlx5/mlx5.c:533: undefined reference 
to `ibv_query_device'
/home/avi/dpdk-stable-17.05.2/drivers/net/mlx5/mlx5.c:829: undefined reference 
to `ibv_close_device'
/home/avi/dpdk-stable-17.05.2/drivers/net/mlx5/mlx5.c:831: undefined reference 
to `ibv_free_device_list'
/home/avi/dpdk-stable-17.05.2/drivers/net/mlx5/mlx5.c:518: undefined reference 
to `ibv_free_device_list'
/home/avi/dpdk-stable-17.05.2/drivers/net/mlx5/mlx5.c:568: undefined reference 
to `ibv_open_device'
/home/avi/dpdk-stable-17.05.2/x86_64-native-linuxapp-gcc/lib/librte_pmd_mlx5.a(mlx5.o):
 In function `___ibv_query_port':
/usr/include/infiniband/verbs.h:1227: undefined reference to `ibv_query_port'
/home/avi/dpdk-stable-17.05.2/x86_64-native-linuxapp-gcc/lib/librte_pmd_mlx5.a(mlx5.o):
 In function `mlx5_pci_probe':
/home/avi/dpdk-stable-17.05.2/drivers/net/mlx5/mlx5.c:591: undefined reference 
to `ibv_alloc_pd'
/home/avi/dpdk-stable-17.05.2/drivers/net/mlx5/mlx5.c:808: undefined reference 
to `ibv_dealloc_pd'
/home/avi/dpdk-stable-17.05.2/drivers/net/mlx5/mlx5.c:810: undefined reference 
to `ibv_close_device'
/home/avi/dpdk-stable-17.05.2/drivers/net/mlx5/mlx5.c:749: undefined reference 
to `ibv_get_device_name'
/home/avi/dpdk-stable-17.05.2/drivers/net/mlx5/mlx5.c:518: undefined reference 
to `ibv_free_device_list'
/home/avi/dpdk-stable-17.05.2/x86_64-native-linuxapp-gcc/lib/librte_pmd_mlx5.a(mlx5.o):
 In function `rte_mlx5_pmd_init':
/home/avi/dpdk-stable-17.05.2/drivers/net/mlx5/mlx5.c:897: undefined reference 
to `ibv_fork_init'
/home/avi/dpdk-stable-17.05.2/x86_64-native-linuxapp-gcc/lib/librte_pmd_mlx5.a(mlx5_rxq.o):
 In function `priv_create_hash_rxqs':
/home/avi/dpdk-stable-17.05.2/drivers/net/mlx5/mlx5_rxq.c:499: undefined 
reference to `ibv_destroy_qp'
/home/avi/dpdk-stable-17.05.2/x86_64-native-linuxapp-gcc/lib/librte_pmd_mlx5.a(mlx5_rxq.o):
 In function `priv_destroy_hash_rxqs':
/home/avi/dpdk-stable-17.05.2/drivers/net/mlx5/mlx5_rxq.c:549: undefined 
reference to `ibv_destroy_qp'
/home/avi/dpdk-stable-17.05.2/x86_64-native-linuxapp-gcc/lib/librte_pmd_mlx5.a(mlx5_rxq.o):
 In function `rxq_cleanup':
/home/avi/dpdk-stable-17.05.2/drivers/net/mlx5/mlx5_rxq.c:754: undefined 
reference to `ibv_destroy_cq'
/home/avi/dpdk-stable-17.05.2/drivers/net/mlx5/mlx5_rxq.c:756: undefined 
reference to `ibv_destroy_comp_channel'
/home/avi/dpdk-stable-17.05.2/drivers/net/mlx5/mlx5_rxq.c:758: undefined 
reference to `ibv_dereg_mr'
/home/avi/dpdk-stable-17.05.2/x86_64-native-linuxapp-gcc/lib/librte_pmd_mlx5.a(mlx5_rxq.o):
 In function `rxq_ctrl_setup':
/home/avi/dpdk-stable-17.05.2/drivers/net/mlx5/mlx5_rxq.c:979: undefined 
reference to `ibv_create_comp_channel'
/home/avi/dpdk-stable-17.05.2/x86_64-native-linuxapp-gcc/lib/librte_pmd_mlx5.a(mlx5_rxq.o):
 In function `mlx5_rx_intr_disable':
/home/avi/dpdk-stable-17.05.2/drivers/net/mlx5/mlx5_rxq.c:1456: undefined 
reference to `ibv_get_cq_event'
/home/avi/dpdk-stable-17.05.2/drivers/net/mlx5/mlx5_rxq.c:1464: undefined 
reference to `ibv_ack_cq_events'
/home/avi/dpdk-stable-17.05.2/x86_64-native-linuxapp-gcc/lib/librte_pmd_mlx5.a(mlx5_txq.o):
 In function `txq_cleanup':
/home/avi/dpdk-stable-17.05.2/drivers/net/mlx5/mlx5_txq.c:148: undefined 
reference to `ibv_destroy_qp'
/home/avi/dpdk-stable-17.05.2/drivers/net/mlx5/mlx5_txq.c:150: undefined 
reference to `ibv_destroy_cq'
/home/avi/dpdk-stable-17.05.2/drivers/net/mlx5/mlx5_txq.c:155: undefined 
reference to `ibv_dereg_mr'
/home/avi/dpdk-stable-17.05.2/x86_64-native-linuxapp-gcc/lib/librte_pmd_mlx5.a(mlx5_txq.o):
 In function `ibv_exp_create_qp':
/usr/include/infiniband/verbs_exp.h:3009: undefined reference to `ibv_create_qp'
/home/avi/dpdk-stable-17.05.2/x86_64-native-linuxapp-gcc/lib/librte_pmd_mlx5.a(mlx5_ethdev.o):
 In function `priv_dev_link_status_handler':
/home/avi/dpdk-stable-17.05.2/drivers/net/mlx5/mlx5_ethdev.c:1240: undefined 
reference to `ibv_ack_async_event'
/home/avi/dpdk-stable-17.05.2/drivers/net/mlx5/mlx5_ethdev.c:1233: undefined 
reference to `ibv_get_async_event'
/home/avi/dpdk-stable-17.05.2/drivers/net/mlx5/mlx5_ethdev.c:1240: undefined 
reference to `ibv_ack_async_event'
/home/avi/dpdk-stable-17.05.2/drivers/net/mlx5/mlx5_ethdev.c:1233: undefined 
referen

Re: [ovs-discuss] OvS build (w DPDK) failed - Undefined Mellanox references

2018-02-20 Thread Olga Shern 
Avi, 

Every DPDK version has specific MLNX_OFED that is supports:
If you will follow the instruction that I sent to you will see that:
Mellanox OFED version should be  4.0-2.0.0.0 and installation should be   
./mlnxofedinstall 
http://dpdk.org/doc/guides-17.05/nics/mlx5.html 

Now, you can stay with MLNX_OFED 4.2, but you will need to reinstall  it 
without --upstream-libs flags.

Starting DPDK 17.11 Mellanox PMDs supports upstream rdma-core libs, therefore 
the installation is different for DPDK versions starting 17.11
Since user shouldn't be aware about this info, user should follow the exact 
instructions!

Best Regards,
Olga

-Original Message-
From: Avi Cohen (A) [mailto:avi.co...@huawei.com] 
Sent: Tuesday, February 20, 2018 1:03 PM
To: Olga Shern ; ovs-discuss@openvswitch.org
Cc: Erez Ferber 
Subject: RE: [ovs-discuss] OvS build (w DPDK) failed - Undefined Mellanox 
references

Olga

I have OFED -  MLNX_OFED_LINUX-4.2-1.2.0.0-ubuntu16.04-x86_64
I install it like this :  ./mlnxofedinstall --force --dpdk --upstream-libs NOTE 
 that I don't have this problem with dpdk.17.11/ dpdk.18.02

Best Regards
Avi



> -Original Message-
> From: Olga Shern [mailto:ol...@mellanox.com]
> Sent: Tuesday, 20 February, 2018 12:19 PM
> To: Avi Cohen (A); ovs-discuss@openvswitch.org
> Cc: Erez Ferber
> Subject: RE: [ovs-discuss] OvS build (w DPDK) failed - Undefined 
> Mellanox references
> 
> Looks like you didn't install MLNX_OFED ir something wrong with your 
> installation, the following file is missing:
> /usr/include/infiniband/mlx5_hw.h
> 
> What OFED did you install and how?
> 
> -Original Message-
> From: Avi Cohen (A) [mailto:avi.co...@huawei.com]
> Sent: Tuesday, February 20, 2018 10:21 AM
> To: Olga Shern ; ovs-discuss@openvswitch.org
> Cc: Erez Ferber 
> Subject: RE: [ovs-discuss] OvS build (w DPDK) failed - Undefined 
> Mellanox references
> 
> Thank you Olga
> What I'm trying to do is to run ovs-dpdk w connectx4 card, I don't 
> care about the versions but only try to  find a  combination of 
> versions (dpdk/ovs/kernel) that is working.
> As you've suggested,  now I'm working with dpdk.17.05 (ovs 2.8.1) .
> I'm following the
> https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fdpdk
> .org
> %2Fdoc%2Fguides-
> 17.05%2Fnics%2Fmlx5.html&data=02%7C01%7Colgas%40mellanox.com%7C45
> 2a99fe115941a1fd0508d5783add13%7Ca652971c7d2e4d9ba6a4d149256f461b
> %7C0%7C0%7C636547116571396518&sdata=YyijRGomnVwvz8epD90ec1lx4YyB
> 2Fn2InZvgK5fqfY%3D&reserved=0
> And I have compilation error when building dpdk  - [ note that  dpdk 
> 18.02 and
> dpdk.17.11 build pass ok, but then ovs failed with undefined mlx ref.]
> 
> Dpdk.17.05 - compilation error:
> --
> In file included from /home/avi/dpdk-stable- 
> 17.05.2/drivers/net/mlx5/mlx5.h:68:0,
> from /home/avi/dpdk-stable-17.05.2/drivers/net/mlx5/mlx5.c:67:
> /home/avi/dpdk-stable-17.05.2/drivers/net/mlx5/mlx5_rxtx.h:46:32: 
> fatal
> error: infiniband/mlx5_hw.h: No such file or directory
> ---
> 
> Best Regards
> Avi
> 
> 
> 
> > -Original Message-
> > From: Olga Shern [mailto:ol...@mellanox.com]
> > Sent: Monday, 19 February, 2018 11:31 PM
> > To: Avi Cohen (A); ovs-discuss@openvswitch.org
> > Cc: Erez Ferber
> > Subject: RE: [ovs-discuss] OvS build (w DPDK) failed - Undefined 
> > Mellanox references
> >
> > Hi Avi,
> >
> > Can you please explain what you are trying to do?
> > Are you trying to test latest  DPDK with OVS 2.8.1?
> > OVS 2.8.1 supports DPDK 17.05.1 , and as far as I know,  it also 
> > working with DPDK 17.08 DPDK 17.11 is supported with OVS 2.9.
> >
> > If you want help regarding DPDK you should send emails to the 
> > us...@dpdk.org
> >
> > Now, regarding what I stated before, you need to follow procedure 
> > from DPDK.org for mlx PMDs :
> > For 17.08:
> > https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fdp
> > dk
> > .org%2Fdoc%2Fguides-
> 17.08%2Fnics%2Fmlx5.html&data=02%7C01%7Colgas%40me
> >
> llanox.com%7C452a99fe115941a1fd0508d5783add13%7Ca652971c7d2e4d9ba
> 6a4d1
> >
> 49256f461b%7C0%7C0%7C636547116571396518&sdata=ITJ%2FVuP09A2911IU
> %2BN%2
> > BQqscF4aYBGl2vYbEK7qU9QfM%3D&reserved=0 , Please go to section 20.7.
> > Quick Start Guide and check section  20.5. Prerequisites MLNX_OFED 
> > 4.1 ./mlnxofedinstall For 17.11:
> > https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fdp
> > dk
> > .org%2Fdoc%2Fguides-
> &data=02%7C01%7Colgas%40mellanox.com%7C452a99fe115
> >
> 941a1fd0508d5783add13%7Ca652971c7d2e4d9ba6a4d149256f461b%7C0%7C0
> %7C636
> >
> 547116571396518&sdata=gxX93MLNYo3vhR0p32hQn37I8yuSm5g4xqsWpBsKQ
> 3U%3D&r
> > eserved=0 17.11/nics/mlx5.html ,  please go to section 21.7 (Quick 
> > Start Guide on OFED) and check section  21.5.1.2. Mellanox OFED for 
> > the right MLNX_OFED to use MLNX_OFED 4.2 ./mlnxofedinstall 
> > --upstream-libs --dpdk
> >
> > Etc ...
> >
> > Hope this helps
> >
> > Best Regards,
> > Olga
> >
> >
> > -Original Me

Re: [ovs-discuss] OvS build (w DPDK) failed - Undefined Mellanox references

2018-02-20 Thread Avi Cohen (A) 
Olga

I have OFED -  MLNX_OFED_LINUX-4.2-1.2.0.0-ubuntu16.04-x86_64
I install it like this :  ./mlnxofedinstall --force --dpdk --upstream-libs
NOTE  that I don't have this problem with dpdk.17.11/ dpdk.18.02

Best Regards
Avi



> -Original Message-
> From: Olga Shern [mailto:ol...@mellanox.com]
> Sent: Tuesday, 20 February, 2018 12:19 PM
> To: Avi Cohen (A); ovs-discuss@openvswitch.org
> Cc: Erez Ferber
> Subject: RE: [ovs-discuss] OvS build (w DPDK) failed - Undefined Mellanox
> references
> 
> Looks like you didn't install MLNX_OFED ir something wrong with your
> installation, the following file is missing:
> /usr/include/infiniband/mlx5_hw.h
> 
> What OFED did you install and how?
> 
> -Original Message-
> From: Avi Cohen (A) [mailto:avi.co...@huawei.com]
> Sent: Tuesday, February 20, 2018 10:21 AM
> To: Olga Shern ; ovs-discuss@openvswitch.org
> Cc: Erez Ferber 
> Subject: RE: [ovs-discuss] OvS build (w DPDK) failed - Undefined Mellanox
> references
> 
> Thank you Olga
> What I'm trying to do is to run ovs-dpdk w connectx4 card, I don't care about
> the versions but only try to  find a  combination of versions 
> (dpdk/ovs/kernel)
> that is working.
> As you've suggested,  now I'm working with dpdk.17.05 (ovs 2.8.1) .
> I'm following the
> https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fdpdk.org
> %2Fdoc%2Fguides-
> 17.05%2Fnics%2Fmlx5.html&data=02%7C01%7Colgas%40mellanox.com%7C45
> 2a99fe115941a1fd0508d5783add13%7Ca652971c7d2e4d9ba6a4d149256f461b
> %7C0%7C0%7C636547116571396518&sdata=YyijRGomnVwvz8epD90ec1lx4YyB
> 2Fn2InZvgK5fqfY%3D&reserved=0
> And I have compilation error when building dpdk  - [ note that  dpdk 18.02 and
> dpdk.17.11 build pass ok, but then ovs failed with undefined mlx ref.]
> 
> Dpdk.17.05 - compilation error:
> --
> In file included from /home/avi/dpdk-stable-
> 17.05.2/drivers/net/mlx5/mlx5.h:68:0,
> from /home/avi/dpdk-stable-17.05.2/drivers/net/mlx5/mlx5.c:67:
> /home/avi/dpdk-stable-17.05.2/drivers/net/mlx5/mlx5_rxtx.h:46:32: fatal
> error: infiniband/mlx5_hw.h: No such file or directory
> ---
> 
> Best Regards
> Avi
> 
> 
> 
> > -Original Message-
> > From: Olga Shern [mailto:ol...@mellanox.com]
> > Sent: Monday, 19 February, 2018 11:31 PM
> > To: Avi Cohen (A); ovs-discuss@openvswitch.org
> > Cc: Erez Ferber
> > Subject: RE: [ovs-discuss] OvS build (w DPDK) failed - Undefined
> > Mellanox references
> >
> > Hi Avi,
> >
> > Can you please explain what you are trying to do?
> > Are you trying to test latest  DPDK with OVS 2.8.1?
> > OVS 2.8.1 supports DPDK 17.05.1 , and as far as I know,  it also
> > working with DPDK 17.08 DPDK 17.11 is supported with OVS 2.9.
> >
> > If you want help regarding DPDK you should send emails to the
> > us...@dpdk.org
> >
> > Now, regarding what I stated before, you need to follow procedure from
> > DPDK.org for mlx PMDs :
> > For 17.08:
> > https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fdpdk
> > .org%2Fdoc%2Fguides-
> 17.08%2Fnics%2Fmlx5.html&data=02%7C01%7Colgas%40me
> >
> llanox.com%7C452a99fe115941a1fd0508d5783add13%7Ca652971c7d2e4d9ba
> 6a4d1
> >
> 49256f461b%7C0%7C0%7C636547116571396518&sdata=ITJ%2FVuP09A2911IU
> %2BN%2
> > BQqscF4aYBGl2vYbEK7qU9QfM%3D&reserved=0 , Please go to section 20.7.
> > Quick Start Guide and check section  20.5. Prerequisites MLNX_OFED 4.1
> > ./mlnxofedinstall For 17.11:
> > https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fdpdk
> > .org%2Fdoc%2Fguides-
> &data=02%7C01%7Colgas%40mellanox.com%7C452a99fe115
> >
> 941a1fd0508d5783add13%7Ca652971c7d2e4d9ba6a4d149256f461b%7C0%7C0
> %7C636
> >
> 547116571396518&sdata=gxX93MLNYo3vhR0p32hQn37I8yuSm5g4xqsWpBsKQ
> 3U%3D&r
> > eserved=0 17.11/nics/mlx5.html ,  please go to section 21.7 (Quick
> > Start Guide on OFED) and check section  21.5.1.2. Mellanox OFED for
> > the right MLNX_OFED to use MLNX_OFED 4.2 ./mlnxofedinstall
> > --upstream-libs --dpdk
> >
> > Etc ...
> >
> > Hope this helps
> >
> > Best Regards,
> > Olga
> >
> >
> > -Original Message-
> > From: ovs-discuss-boun...@openvswitch.org [mailto:ovs-discuss-
> > boun...@openvswitch.org] On Behalf Of Avi Cohen (A)
> > Sent: Monday, February 19, 2018 6:21 PM
> > To: ovs-discuss@openvswitch.org
> > Subject: [ovs-discuss] OvS build (w DPDK) failed - Undefined Mellanox
> > references
> >
> > Hi,
> > I build dpdk-18.02 with MLX5_PMD - ok..
> > Then I failed to build ovs - 2.8.1]  with dpdk and get many undefined
> > reference for mlx I have mellanox OFED installed
> >
> > Some of the errors here :
> >
> >
> > /home/avi/dpdk-18.02/x86_64-native-linuxapp-
> > gcc/lib/librte_pmd_mlx5.a(mlx5_glue.o): In function `mlx5_glue_dv_init_obj':
> > /home/avi/dpdk-18.02/drivers/net/mlx5/mlx5_glue.c:307: undefined
> > reference to `mlx5dv_init_obj'
> > /home/avi/dpdk-18.02/x86_64-native-linuxapp-
> > gcc/lib/librte_pmd_mlx5.a(mlx5_glue.o): In function
> > `mlx5_glue_dv_set_context_attr':
> > /home/avi/dpdk-18.02/drivers/ne

Re: [ovs-discuss] OvS build (w DPDK) failed - Undefined Mellanox references

2018-02-20 Thread Olga Shern 
Looks like you didn't install MLNX_OFED ir something wrong with your 
installation, the following file is missing: 
/usr/include/infiniband/mlx5_hw.h

What OFED did you install and how? 

-Original Message-
From: Avi Cohen (A) [mailto:avi.co...@huawei.com] 
Sent: Tuesday, February 20, 2018 10:21 AM
To: Olga Shern ; ovs-discuss@openvswitch.org
Cc: Erez Ferber 
Subject: RE: [ovs-discuss] OvS build (w DPDK) failed - Undefined Mellanox 
references

Thank you Olga
What I'm trying to do is to run ovs-dpdk w connectx4 card, I don't care about 
the versions but only try to  find a  combination of versions (dpdk/ovs/kernel) 
that is working.
As you've suggested,  now I'm working with dpdk.17.05 (ovs 2.8.1) .
I'm following the 
https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fdpdk.org%2Fdoc%2Fguides-17.05%2Fnics%2Fmlx5.html&data=02%7C01%7Colgas%40mellanox.com%7C452a99fe115941a1fd0508d5783add13%7Ca652971c7d2e4d9ba6a4d149256f461b%7C0%7C0%7C636547116571396518&sdata=YyijRGomnVwvz8epD90ec1lx4YyB2Fn2InZvgK5fqfY%3D&reserved=0
And I have compilation error when building dpdk  - [ note that  dpdk 18.02 and 
dpdk.17.11 build pass ok, but then ovs failed with undefined mlx ref.]

Dpdk.17.05 - compilation error:
--
In file included from 
/home/avi/dpdk-stable-17.05.2/drivers/net/mlx5/mlx5.h:68:0,
from /home/avi/dpdk-stable-17.05.2/drivers/net/mlx5/mlx5.c:67:
/home/avi/dpdk-stable-17.05.2/drivers/net/mlx5/mlx5_rxtx.h:46:32: fatal error: 
infiniband/mlx5_hw.h: No such file or directory
---

Best Regards
Avi
 


> -Original Message-
> From: Olga Shern [mailto:ol...@mellanox.com]
> Sent: Monday, 19 February, 2018 11:31 PM
> To: Avi Cohen (A); ovs-discuss@openvswitch.org
> Cc: Erez Ferber
> Subject: RE: [ovs-discuss] OvS build (w DPDK) failed - Undefined 
> Mellanox references
> 
> Hi Avi,
> 
> Can you please explain what you are trying to do?
> Are you trying to test latest  DPDK with OVS 2.8.1?
> OVS 2.8.1 supports DPDK 17.05.1 , and as far as I know,  it also 
> working with DPDK 17.08 DPDK 17.11 is supported with OVS 2.9.
> 
> If you want help regarding DPDK you should send emails to the 
> us...@dpdk.org
> 
> Now, regarding what I stated before, you need to follow procedure from 
> DPDK.org for mlx PMDs :
> For 17.08: 
> https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fdpdk
> .org%2Fdoc%2Fguides-17.08%2Fnics%2Fmlx5.html&data=02%7C01%7Colgas%40me
> llanox.com%7C452a99fe115941a1fd0508d5783add13%7Ca652971c7d2e4d9ba6a4d1
> 49256f461b%7C0%7C0%7C636547116571396518&sdata=ITJ%2FVuP09A2911IU%2BN%2
> BQqscF4aYBGl2vYbEK7qU9QfM%3D&reserved=0 , Please go to section 20.7. 
> Quick Start Guide and check section  20.5. Prerequisites MLNX_OFED 4.1 
> ./mlnxofedinstall For 17.11: 
> https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fdpdk
> .org%2Fdoc%2Fguides-&data=02%7C01%7Colgas%40mellanox.com%7C452a99fe115
> 941a1fd0508d5783add13%7Ca652971c7d2e4d9ba6a4d149256f461b%7C0%7C0%7C636
> 547116571396518&sdata=gxX93MLNYo3vhR0p32hQn37I8yuSm5g4xqsWpBsKQ3U%3D&r
> eserved=0 17.11/nics/mlx5.html ,  please go to section 21.7 (Quick 
> Start Guide on OFED) and check section  21.5.1.2. Mellanox OFED for 
> the right MLNX_OFED to use MLNX_OFED 4.2 ./mlnxofedinstall 
> --upstream-libs --dpdk
> 
> Etc ...
> 
> Hope this helps
> 
> Best Regards,
> Olga
> 
> 
> -Original Message-
> From: ovs-discuss-boun...@openvswitch.org [mailto:ovs-discuss- 
> boun...@openvswitch.org] On Behalf Of Avi Cohen (A)
> Sent: Monday, February 19, 2018 6:21 PM
> To: ovs-discuss@openvswitch.org
> Subject: [ovs-discuss] OvS build (w DPDK) failed - Undefined Mellanox 
> references
> 
> Hi,
> I build dpdk-18.02 with MLX5_PMD - ok..
> Then I failed to build ovs - 2.8.1]  with dpdk and get many undefined 
> reference for mlx I have mellanox OFED installed
> 
> Some of the errors here :
> 
> 
> /home/avi/dpdk-18.02/x86_64-native-linuxapp-
> gcc/lib/librte_pmd_mlx5.a(mlx5_glue.o): In function `mlx5_glue_dv_init_obj':
> /home/avi/dpdk-18.02/drivers/net/mlx5/mlx5_glue.c:307: undefined 
> reference to `mlx5dv_init_obj'
> /home/avi/dpdk-18.02/x86_64-native-linuxapp-
> gcc/lib/librte_pmd_mlx5.a(mlx5_glue.o): In function
> `mlx5_glue_dv_set_context_attr':
> /home/avi/dpdk-18.02/drivers/net/mlx5/mlx5_glue.c:301: undefined 
> reference to `mlx5dv_set_context_attr'
> /home/avi/dpdk-18.02/x86_64-native-linuxapp-
> gcc/lib/librte_pmd_mlx5.a(mlx5_glue.o): In function
> `mlx5_glue_dv_query_device':
> /home/avi/dpdk-18.02/drivers/net/mlx5/mlx5_glue.c:294: undefined 
> reference to `mlx5dv_query_device'
> /home/avi/dpdk-18.02/x86_64-native-linuxapp-
> gcc/lib/librte_pmd_mlx5.a(mlx5_glue.o): In function
> `mlx5_glue_dv_create_cq':
> /home/avi/dpdk-18.02/drivers/net/mlx5/mlx5_glue.c:287: undefined 
> reference to `mlx5dv_create_cq'
> /home/avi/dpdk-18.02/x86_64-native-linuxapp-
> gcc/lib/librte_pmd_mlx5.a(mlx5_glue.o): In function
> `mlx5_glue_port_state_str':
> /home/avi/dpdk-18.02/drivers/net/mlx5/mlx5_glue.c:

Re: [ovs-discuss] OvS build (w DPDK) failed - Undefined Mellanox references

2018-02-20 Thread Avi Cohen (A) 
Thank you Olga
What I'm trying to do is to run ovs-dpdk w connectx4 card, I don't care about 
the versions but only try to  find a  combination of versions (dpdk/ovs/kernel) 
that is working.
As you've suggested,  now I'm working with dpdk.17.05 (ovs 2.8.1) .
I'm following the http://dpdk.org/doc/guides-17.05/nics/mlx5.html
And I have compilation error when building dpdk  - [ note that  dpdk 18.02 and 
dpdk.17.11 build pass ok, but then ovs failed with undefined mlx ref.]

Dpdk.17.05 - compilation error:
--
In file included from 
/home/avi/dpdk-stable-17.05.2/drivers/net/mlx5/mlx5.h:68:0,
from /home/avi/dpdk-stable-17.05.2/drivers/net/mlx5/mlx5.c:67:
/home/avi/dpdk-stable-17.05.2/drivers/net/mlx5/mlx5_rxtx.h:46:32: fatal error: 
infiniband/mlx5_hw.h: No such file or directory
---

Best Regards
Avi
 


> -Original Message-
> From: Olga Shern [mailto:ol...@mellanox.com]
> Sent: Monday, 19 February, 2018 11:31 PM
> To: Avi Cohen (A); ovs-discuss@openvswitch.org
> Cc: Erez Ferber
> Subject: RE: [ovs-discuss] OvS build (w DPDK) failed - Undefined Mellanox
> references
> 
> Hi Avi,
> 
> Can you please explain what you are trying to do?
> Are you trying to test latest  DPDK with OVS 2.8.1?
> OVS 2.8.1 supports DPDK 17.05.1 , and as far as I know,  it also working with
> DPDK 17.08 DPDK 17.11 is supported with OVS 2.9.
> 
> If you want help regarding DPDK you should send emails to the us...@dpdk.org
> 
> Now, regarding what I stated before, you need to follow procedure from
> DPDK.org for mlx PMDs :
> For 17.08: http://dpdk.org/doc/guides-17.08/nics/mlx5.html , Please go to
> section 20.7. Quick Start Guide and check section  20.5. Prerequisites
> MLNX_OFED 4.1 ./mlnxofedinstall For 17.11: http://dpdk.org/doc/guides-
> 17.11/nics/mlx5.html ,  please go to section 21.7 (Quick Start Guide on OFED)
> and check section  21.5.1.2. Mellanox OFED for the right MLNX_OFED to use
> MLNX_OFED 4.2 ./mlnxofedinstall --upstream-libs --dpdk
> 
> Etc ...
> 
> Hope this helps
> 
> Best Regards,
> Olga
> 
> 
> -Original Message-
> From: ovs-discuss-boun...@openvswitch.org [mailto:ovs-discuss-
> boun...@openvswitch.org] On Behalf Of Avi Cohen (A)
> Sent: Monday, February 19, 2018 6:21 PM
> To: ovs-discuss@openvswitch.org
> Subject: [ovs-discuss] OvS build (w DPDK) failed - Undefined Mellanox
> references
> 
> Hi,
> I build dpdk-18.02 with MLX5_PMD - ok..
> Then I failed to build ovs - 2.8.1]  with dpdk and get many undefined 
> reference
> for mlx I have mellanox OFED installed
> 
> Some of the errors here :
> 
> 
> /home/avi/dpdk-18.02/x86_64-native-linuxapp-
> gcc/lib/librte_pmd_mlx5.a(mlx5_glue.o): In function `mlx5_glue_dv_init_obj':
> /home/avi/dpdk-18.02/drivers/net/mlx5/mlx5_glue.c:307: undefined reference
> to `mlx5dv_init_obj'
> /home/avi/dpdk-18.02/x86_64-native-linuxapp-
> gcc/lib/librte_pmd_mlx5.a(mlx5_glue.o): In function
> `mlx5_glue_dv_set_context_attr':
> /home/avi/dpdk-18.02/drivers/net/mlx5/mlx5_glue.c:301: undefined reference
> to `mlx5dv_set_context_attr'
> /home/avi/dpdk-18.02/x86_64-native-linuxapp-
> gcc/lib/librte_pmd_mlx5.a(mlx5_glue.o): In function
> `mlx5_glue_dv_query_device':
> /home/avi/dpdk-18.02/drivers/net/mlx5/mlx5_glue.c:294: undefined reference
> to `mlx5dv_query_device'
> /home/avi/dpdk-18.02/x86_64-native-linuxapp-
> gcc/lib/librte_pmd_mlx5.a(mlx5_glue.o): In function
> `mlx5_glue_dv_create_cq':
> /home/avi/dpdk-18.02/drivers/net/mlx5/mlx5_glue.c:287: undefined reference
> to `mlx5dv_create_cq'
> /home/avi/dpdk-18.02/x86_64-native-linuxapp-
> gcc/lib/librte_pmd_mlx5.a(mlx5_glue.o): In function
> `mlx5_glue_port_state_str':
> /home/avi/dpdk-18.02/drivers/net/mlx5/mlx5_glue.c:273: undefined reference
> to `ibv_port_state_str'
> /home/avi/dpdk-18.02/x86_64-native-linuxapp-
> gcc/lib/librte_pmd_mlx5.a(mlx5_glue.o): In function
> `mlx5_glue_get_async_event':
> /home/avi/dpdk-18.02/drivers/net/mlx5/mlx5_glue.c:267: undefined reference
> to `ibv_get_async_event'
> /home/avi/dpdk-18.02/x86_64-native-linuxapp-
> gcc/lib/librte_pmd_mlx5.a(mlx5_glue.o): In function
> `mlx5_glue_ack_async_event':
> /home/avi/dpdk-18.02/drivers/net/mlx5/mlx5_glue.c:260: undefined reference
> to `ibv_ack_async_event'
> /home/avi/dpdk-18.02/x86_64-native-linuxapp-
> gcc/lib/librte_pmd_mlx5.a(mlx5_glue.o): In function `mlx5_glue_dereg_mr':
> 
> Who can help ?
> Best Regards
> Avi
> ___
> discuss mailing list
> disc...@openvswitch.org
> https://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmail.op
> envswitch.org%2Fmailman%2Flistinfo%2Fovs-
> discuss&data=02%7C01%7Colgas%40mellanox.com%7Cbd7017779e624a247e3
> 508d577b4d322%7Ca652971c7d2e4d9ba6a4d149256f461b%7C0%7C0%7C6365
> 46540872320081&sdata=qPOVcZSoBvPQzpSKw9632jOC0iRhPwpnGdULr3u8KU
> Q%3D&reserved=0
___
discuss mailing list
disc...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-discuss