[ovs-discuss] OVS megaflows

[Sara Gittlin]

Hello,
I understand that there is a support for megaflows in the kernel and netlink.
I also understand that there is no megaflow implementation in ofproto.
i.e. there is no implementation of compressing (if possible) all flows
in ofproto table to megaflows and installing it in the datapath. is
that correct ?
Thanks in advance - Sara
___
discuss mailing list
disc...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-discuss

Re: [ovs-discuss] Issue with offloading OVS flows into Mellanox-4 cards

[Sugu Deepthy]

Hi Roi,
Thank you for  your reply.
Sorry for not getting back on this before. Was held up in some other stuff.
Please find my answers below.

On Wed, Jul 12, 2017 at 5:33 AM, Roi Dayan  wrote:

>
>
> On 11/07/2017 14:28, Sugu Deepthy wrote:
>
>> Hi Roi
>>
>> On Tue, Jul 11, 2017 at 12:20 AM, Sugu Deepthy > > wrote:
>>
>> Thank you Roi for your help!
>>
>> On Mon, Jul 10, 2017 at 4:57 AM, Roi Dayan > > wrote:
>>
>>
>>
>> On 07/07/2017 17:36, Sugu Chandran wrote:
>>
>> Hi,
>>
>> I am trying to test hardware offloading feature in OVS using
>> a 2*25G
>> mellanox NIC.   My test setup has static OVS L2 rules to
>> forward packets
>> between these two ports. The traffic generators are
>> connected to these
>> ports to pump in traffic.
>> The hardware offloading is enabled in the system by using,
>> ovs-vsctl --no-wait set Open_vSwitch .
>> other_config:hw-offload=true
>> I didnt set any hw-policy explicit,  as I kept it default as
>> 'None'
>>
>> I noticed that when I am sending traffic to these ports,
>> there are no
>> rules that are getting programmed into the hardware. Also
>> there are no
>> error reported in ovs-vswitchd.log as such.
>> Of Course the packets are getting forwarded in software.  Is
>> there
>> anything else needs to be done to make the TC for
>> programming the
>> mellanox NICs?
>>
>> Regards
>> _Sugu
>>
>>
>>
>> Hi Sugo,
>>
>> Since you do not have errors in the log did you check if the rules
>> were added to tc software?
>> you can dump like this:
>> # tc -s filter show dev ens5f0 ingress
>>
>> I dont see any rules that are configured with above tc dump.
>>
>>
> then nothing went to the HCA because even if the HW doesn't
> support it the rule should be in tc software.

[Sugesh] Yes thats right.

>
>
>>
>> You need to enable the offload feature on the HCA with ethtool.
>> example:
>> # ethtool -K ens5f0 hw-tc-offload on
>>
>> This is enabled .
>>
>> I am trying to forward traffic between two PFs on the same NIC?
>> Does it supported in the offload implementation?
>>
>
> offload between PF ports is currently not supported.
> only PF and its VFs.

[Sugu]
Ok. I am trying to do the traffic forwarding between PF and VFs . But no
luck so far.

>
>
>
> When creating the switchdev on PFs with 2 VFs, there is no VF
>> netdevs are populated in my system. They are still showing as the
>> vfs under the PF.
>> Ofcourse there are no errors too.
>>
>> Also the system reports the mode 'inline-mode transport'is
>> unsupported.
>> I am using ubunutu 17.04 with 4.10 kernel.
>> Is there anything I am missing here?
>> Any help is really appreciated!.
>>
>> [Sugu] Some more details on this. I was really getting error when trying
>> to enable hw-offload on mlnx-4 NICs.
>> Didnt notice in the logs before.
>>
>> This the error info that I got from mellanox git.
>>
>> BAD_SYS_STATE | 0x368B01 | query_vport_counter: vport is not enabled
>> (INIT_HCA is required)
>>
>
> executing which command raised this error?

[Sugu] I upgraded the system and now I dont see this error anymore. Instead
I see this

[ 1103.216355] mlx5_3:wait_for_async_commands:722:(pid 3097): done with all
pending requests
[ 1115.954770] mlx5_core :07:00.0: mlx5_cmd_check:697:(pid 3477):
QUERY_VPORT_COUNTER(0x770) op_mod(0x0) failed, status bad system
state(0x4), syndrome (0x368b01)
[ 1115.954902] mlx5_core :07:00.0: mlx5_cmd_check:697:(pid 3477):
QUERY_VPORT_COUNTER(0x770) op_mod(0x0) failed, status bad system
state(0x4), syndrome (0x368b01)

I am getting this error back to back for every command(2 entry for each
command as I have 2 VFs, may be?)
starting from unbind, devlink, ethtool and starting the VM.
And inside the VM the VFs are not bound to any driver either. Is there any
wrong with the NIC?



>
>
>
>> I verfied that the ports named eth1, eth2, eth3 and et4 are created for
>> my vfs, when
>> I ran the commands 'devlink dev eswitch set pci/:07:00.0 mode
>> switchdev' and
>> 'devlink dev eswitch set pci/:07:00.1 mode switchdev'
>>
>> The detailed error in dmesg are given below,
>> [ 1245.941287] mlx5_core :07:00.0: mlx5_cmd_check:697:(pid 3107):
>> QUERY_VPORT_COUNTER(0x770) op_mod(0x0) failed, status bad system
>> state(0x4), syndrome (0x368b01)
>> [ 1245.941478] mlx5_core :07:00.1: mlx5_cmd_check:697:(pid 3107):
>> QUERY_VPORT_COUNTER(0x770) op_mod(0x0) failed, status bad system
>> state(0x4), syndrome (0x368b01)
>>
>> Please note I couldn't run the "inline-mode transport" command as its
>> not supported.
>>
>>
> maybe you need newer

Re: [ovs-discuss] Added interface to bridge gets added unexpectedly a second time by OVS

[Kevin Benton]

For more info, we had been running into this issue when immediately trying
to set the MAC address on a port right after it was created.

Nobody was able to figure out why the port would disappear from OVS and
then re-appear so we ended up merging an ugly hack to deal with it:
https://github.com/openstack/neutron/commit/a75ce6850f3954edafbb0c128750e39b57875743

Here is the bug report that has some more info:
https://bugs.launchpad.net/neutron/+bug/1618987

On Wed, Jul 12, 2017 at 12:10 PM, Miguel A Lavalle 
wrote:

> Hi,
>
> I am debugging failures in OpenStack Neutron functional tests. The
> sequence of events is the following:
>
> 1) An interface is added successfully to a bridge
>
> 2) The addition of the interface is logged by ovs-vswitchd
>
> 3) The test fails because it cannot find the interface when trying to move
> it to a linux namespace
>
> 4) ovs-vswitchd logs a second time the addition of the interface to the
> bridge
>
> These are the relevant entries from the ovs-vswitchd and the functional
> test logs (the INFO level entries come from ovs-vswitchd):
> http://paste.openstack.org/show/615193/
>
> OVS version from the ovs-vswitchd:
>
> 2017-07-12T07:56:31.554Z|6|bridge|INFO|ovs-vswitchd (Open vSwitch) 2.5.2
>
>
> Miguel A. Lavalle
> OpenStack Neutron Software Developement Lead
> Linux Technology Center
>
>
> ___
> discuss mailing list
> disc...@openvswitch.org
> https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
>
>


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

[ovs-discuss] OVN OpenStack Tutorial

[Christopher Wiedmaier]

I am following the OVN OpenStack tutorial
http://docs.openvswitch.org/en/latest/tutorials/ovn-openstack/ but I am
unable to initialize devstack.  After running stack.sh I receive the
following error,

No package kernel-devel-3.10.0_514.26.2.e17.x86_64 available.

I tried to fix the error by running yum install kernel-devel and the
following is the output

Package kernel-devel-3.10.0-514.26.2.e17.x86_64 already exists.

After rerunning stach.sh I still receive the same error.  Not sure if the
script is looking for a package name with an "underscore" in the package
name when the correct package name uses a hyphen.

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

[ovs-discuss] 802.1ad (QinQ) Support

[Sudhanshu Gupta]

Hi,

I want to know whether double vlan tagged packets are supported in OVS
release 2.7.1 ?

If not, which version of OVS supports double vlan tagged packets?

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

[ovs-discuss] About ovs-docker

[Zekeriya Akgül]

Hi,
I am student on Necmettin Erbakan Universty in Turkey.And working on
communication between dpdk powered openvswitch and docker.And some issues
occured about communication between docker and other hosts.

I explained my problem in this post:
https://superuser.com/questions/1231090/connected-with-open-
v-switch-connection-issue-between-docker-container-and-othe

Please response this post or response me by e-mail.

Thank you!

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

Re: [ovs-discuss] Added interface to bridge gets added unexpectedly a second time by OVS

[Kevin Benton]

For more info, we had been running into this issue when immediately trying
to set the MAC address on a port right after it was created.

Nobody was able to figure out why the port would disappear from OVS and
then re-appear so we ended up merging an ugly hack to deal with it:
https://github.com/openstack/neutron/commit/a75ce6850f3954edafbb0c128750e39b57875743

Here is the bug report that has some more info:
https://bugs.launchpad.net/neutron/+bug/1618987

On Wed, Jul 12, 2017 at 12:10 PM, Miguel A Lavalle 
wrote:

> Hi,
>
> I am debugging failures in OpenStack Neutron functional tests. The
> sequence of events is the following:
>
> 1) An interface is added successfully to a bridge
>
> 2) The addition of the interface is logged by ovs-vswitchd
>
> 3) The test fails because it cannot find the interface when trying to move
> it to a linux namespace
>
> 4) ovs-vswitchd logs a second time the addition of the interface to the
> bridge
>
> These are the relevant entries from the ovs-vswitchd and the functional
> test logs (the INFO level entries come from ovs-vswitchd):
> http://paste.openstack.org/show/615193/
>
> OVS version from the ovs-vswitchd:
>
> 2017-07-12T07:56:31.554Z|6|bridge|INFO|ovs-vswitchd (Open vSwitch) 2.5.2
>
>
> Miguel A. Lavalle
> OpenStack Neutron Software Developement Lead
> Linux Technology Center
>
>
> ___
> 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] Issue with offloading OVS flows into Mellanox-4 cards

[Roi Dayan]

On 24/07/2017 00:36, Sugu Deepthy wrote:

Hi Roi,
Thank you for  your reply.
Sorry for not getting back on this before. Was held up in some other stuff.
Please find my answers below.

On Wed, Jul 12, 2017 at 5:33 AM, Roi Dayan mailto:r...@mellanox.com>> wrote:



On 11/07/2017 14:28, Sugu Deepthy wrote:

Hi Roi

On Tue, Jul 11, 2017 at 12:20 AM, Sugu Deepthy
mailto:deepthysug...@gmail.com>
>> wrote:

Thank you Roi for your help!

On Mon, Jul 10, 2017 at 4:57 AM, Roi Dayan
mailto:r...@mellanox.com>
>> wrote:



On 07/07/2017 17:36, Sugu Chandran wrote:

Hi,

I am trying to test hardware offloading feature in
OVS using
a 2*25G
mellanox NIC.   My test setup has static OVS L2 rules to
forward packets
between these two ports. The traffic generators are
connected to these
ports to pump in traffic.
The hardware offloading is enabled in the system by
using,
ovs-vsctl --no-wait set Open_vSwitch .
other_config:hw-offload=true
I didnt set any hw-policy explicit,  as I kept it
default as
'None'

I noticed that when I am sending traffic to these ports,
there are no
rules that are getting programmed into the hardware.
Also
there are no
error reported in ovs-vswitchd.log as such.
Of Course the packets are getting forwarded in
software.  Is
there
anything else needs to be done to make the TC for
programming the
mellanox NICs?

Regards
_Sugu



Hi Sugo,

Since you do not have errors in the log did you check if
the rules
were added to tc software?
you can dump like this:
# tc -s filter show dev ens5f0 ingress

I dont see any rules that are configured with above tc dump.


then nothing went to the HCA because even if the HW doesn't
support it the rule should be in tc software.

[Sugesh] Yes thats right.




You need to enable the offload feature on the HCA with
ethtool.
example:
# ethtool -K ens5f0 hw-tc-offload on

This is enabled .

I am trying to forward traffic between two PFs on the same NIC?
Does it supported in the offload implementation?


offload between PF ports is currently not supported.
only PF and its VFs.

[Sugu]
Ok. I am trying to do the traffic forwarding between PF and VFs . But no
luck so far.




When creating the switchdev on PFs with 2 VFs, there is no VF
netdevs are populated in my system. They are still showing
as the
vfs under the PF.
Ofcourse there are no errors too.

Also the system reports the mode 'inline-mode transport'is
unsupported.
I am using ubunutu 17.04 with 4.10 kernel.
Is there anything I am missing here?
Any help is really appreciated!.

[Sugu] Some more details on this. I was really getting error
when trying
to enable hw-offload on mlnx-4 NICs.
Didnt notice in the logs before.

This the error info that I got from mellanox git.

BAD_SYS_STATE | 0x368B01 | query_vport_counter: vport is not enabled
(INIT_HCA is required)


executing which command raised this error?

[Sugu] I upgraded the system and now I dont see this error anymore.
Instead I see this

[ 1103.216355] mlx5_3:wait_for_async_commands:722:(pid 3097): done with
all pending requests
[ 1115.954770] mlx5_core :07:00.0: mlx5_cmd_check:697:(pid 3477):
QUERY_VPORT_COUNTER(0x770) op_mod(0x0) failed, status bad system
state(0x4), syndrome (0x368b01)
[ 1115.954902] mlx5_core :07:00.0: mlx5_cmd_check:697:(pid 3477):
QUERY_VPORT_COUNTER(0x770) op_mod(0x0) failed, status bad system
state(0x4), syndrome (0x368b01)

I am getting this error back to back for every command(2 entry for each
command as I have 2 VFs, may be?)
starting from unbind, devlink, ethtool and starting the VM.
And inside the VM the VFs are not bound to any driver either. Is there
any wrong with the NIC?



looks like the syndrome you get is caused by querying a counter while
the HCA is not yes configured properly.
can you verify you are using the latest firmware?
can you verify the steps you do? did you enable sriov and moved to
switchdev