date:20170321

Re: [ovs-discuss] OVS-DPDK

2017-03-21 Thread Darrell Ball

Regarding the question:

“Also, what is OVS-2.6.1's version on options:dpdk-devargs='', by that I 
mean, how does the dpdk port know which interface should it bind to when its 
not specified.. “

Here is a previous thread that answers this question:
https://mail.openvswitch.org/pipermail/ovs-discuss/2016-March/040190.html

We could document this in OVS DPDK as it is function impacting.


From: Advith Nagappa 
Date: Tuesday, March 21, 2017 at 2:46 PM
To: "Stokes, Ian" 
Cc: Darrell Ball , "disc...@openvswitch.org" 

Subject: Re: [ovs-discuss] OVS-DPDK

Hi Ian,

Yes, I am using OVS-2.6.1 release.

And yes, you are correct.

ovs-vsctl add-port br0 dpdk-p1 -- set Interface dpdk-p1 type=dpdk, infact fails 
in 2.6.1;

whereas, ovs-vsctl add-port br0 dpdk1 -- set Interface dpdk1 type=dpdk, 
succeeds.


As regards the use of

options:dpdk-devargs=:00:0a.0

It is only needed if you are using arbitrary port naming/hotplug support which 
is included in OVS 2.7.0.

This answers my query.

But, If i may continue to ask a related query: from the dpdk log..

2017-03-21T03:14:01Z|7|dpdk|INFO|EAL ARGS: ovs-vswitchd --socket-mem 1024,0 
-c 0x0001
EAL: Detected 5 lcore(s)
EAL: Probing VFIO support...
EAL: WARNING: cpu flags constant_tsc=yes nonstop_tsc=no -> using unreliable 
clock cycles !
EAL: PCI device :00:07.0 on NUMA socket -1
EAL:   probe driver: 8086:154c net_i40e_vf
EAL: PCI device :00:09.0 on NUMA socket -1
EAL:   probe driver: 8086:1572 net_i40e
PMD: eth_i40e_dev_init(): FW 5.0 API 1.5 NVM 05.00.02 eetrack 80002284
EAL: PCI device :00:0a.0 on NUMA socket -1
EAL:   probe driver: 8086:1572 net_i40e
PMD: eth_i40e_dev_init(): FW 5.0 API 1.5 NVM 05.00.02 eetrack 80002284


Since I have done the binding 09.0 and 0a.0 to igb_uio driver, shouldn't we see 
'igb_uio' instead of 'net_i40e'?

Also, what is OVS-2.6.1's version on options:dpdk-devargs='', by that I 
mean, how does the dpdk port know which interface should it bind to when its 
not specified..
Here is a previous thread that answers this question:
https://mail.openvswitch.org/pipermail/ovs-discuss/2016-March/040190.html

Best Regards
Advith Nagappa







On Mar 21, 2017 12:00 PM, "Stokes, Ian" 
> wrote:
Apologies for top posting,

Hi Advith, there seems to be a mismatch of OVS versions and expected features 
from the details you have provided.

To confirm you are using OVS 2.6.1? Is there a specific commit ID you are 
using? Or are you using the 2.6.1 tag or release package?

From the commands you have provided it looks like your trying to add dpdk ports 
with arbitrary names and PCI addresses.

This is not possible in OVS 2.6.1, this ability was only added as of OVS 2.7.0.

If you wanted to add 2 physical dpdk ports with 2.6.1 can you try the following

ovs-vsctl add-port br0 dpdk0 -- set Interface dpdk0 type=dpdk
ovs-vsctl add-port br0 dpdk1 -- set Interface dpdk1 type=dpdk

Note the name of the dpdk port must start with dpdk followed by the number 
being added (starting at 0). This is a limitation that has since been removed 
in OVS 2.7.

I’m surprised that you say you can use

ovs-vsctl add-port br0 dpdk-p1 -- set Interface dpdk-p1 type=dpdk

Testing OVS 2.6.1 tag on master with that command returned the vsctl error

ovs-vsctl: Error detected while setting up 'dpdk-p1'.  See ovs-vswitchd log for 
details.

for myself which would be expected.

As regards the use of

options:dpdk-devargs=:00:0a.0

It is only needed if you are using arbitrary port naming/hotplug support which 
is included in OVS 2.7.0.

If you can give these suggestions a shot it will help narrow down the issue at 
hand.

Regards
Ian

From: 
ovs-discuss-boun...@openvswitch.org 
[mailto:ovs-discuss-boun...@openvswitch.org]
 On Behalf Of Advith Nagappa
Sent: Tuesday, March 21, 2017 8:12 AM
To: Darrell Ball >
Cc: disc...@openvswitch.org
Subject: Re: [ovs-discuss] OVS-DPDK

I don’t see the pci memory mapping logs here.
Can you also attach the full dpdk logs ?

I have attached the dpdk-log.

For PCI mapping, may below helps:



Bus info  Device  Class  Description

pci@:00:07.0  ens7network
XL710/X710 Virtual Function
pci@:00:09.0  networkEthernet 
Controller X710 for 10GbE   
   SFP+
pci@:00:0a.0  networkEthernet 
Controller X710 for 10GbE   
  SFP+
 br0 networkEthernet interface

Re: [ovs-discuss] Reinstall OVS from git repo

2017-03-21 Thread 蘇于倫

Hi Guru,

It shows only one instance.
Does it make sense if I have re-installed OVS?

Ethan


2017年3月22日 01:04，"Guru Shetty" 寫道：



On 21 March 2017 at 09:01, 蘇于倫  wrote:

> Hi everyone,
>
> I'd like to confirm which steps should I do to completely remove current
> OVS if I want to re-install OVS with modified C code in git repo ?
>
> Currently what my reinstall_ovs.sh does for old OVS removal is:
> sudo /usr/local/share/openvswitch/scripts/ovs-ctl stop
> sudo rm /usr/local/etc/openvswitch/conf.db
> ps aux | awk '/[o]vs-vswitchd/ {print $2}'
> rm -rf ovs/
>
> Are the steps above sufficient to completely remove OVS installation?
> After I run the re-install script, the code modification does not take
> effect. I modified in-band.c that output port of hidden flow is assigned
> to be the port number I want 0x1 for eth0. However, the hidden
> flows still show NORMAL action.
> Appreciate comments and suggestion!
>

Does 'find /usr -name ovs-vsctl' show 2 instances?


> thanks in advance
>
> Regards.
> Ethan
>
> ___
> 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] OVS+DPDK: socket permissions' problem

2017-03-21 Thread Darrell Ball

From:  on behalf of Aynur Shakirov 

Date: Tuesday, March 21, 2017 at 6:17 AM
To: "ovs-discuss@openvswitch.org" 
Subject: [ovs-discuss] OVS+DPDK: socket permissions' problem

Hello.
Meta.
OVS ver: 2.7.90, today master (stp tests skipped)
Compiler: GCC 5.3.1, default flags
DPDK: 16.11.1 (from Ubuntu Cloud Archive: Ocata)
Env: Ubuntu 16.04.1 up-to-date.
Kernel: 4.8.0-41-generic

Problem.
When I adds a vhost-interface into bridge OVS specifies incorrect rights for 
the socket:

root@dpdk-compute0:/opt/build# ovs-vsctl add-port br-ex vhost-user-1 -- set 
Interface vhost-user-1 type=dpdkvhostuser

2017-03-21T12:09:33.436Z|00115|dpdk|INFO|VHOST_CONFIG: vhost-user server: 
socket created, fd: 46
2017-03-21T12:09:33.436Z|00116|dpdk|INFO|VHOST_CONFIG: bind to 
/var/run/openvswitch/vhost-user-1
2017-03-21T12:09:33.436Z|00117|dpdk|INFO|EAL: Socket 
/var/run/openvswitch/vhost-user-1 changed permissions to 
2017-03-21T12:09:33.436Z|00118|dpdk|ERR|EAL: user �ƿ not found,  aborting.
2017-03-21T12:09:33.436Z|00119|dpdk|ERR|EAL: vhost-user socket unable to get 
specified user/group: �ƿ

This worked better for me. I am using similar ovs and dpdk versions, but older 
kernel
and distro 3.16.0-77-generic #99~14.04.1-Ubuntu.

.
.
2017-03-21T23:09:21.662Z|00104|netdev_dpdk|INFO|Socket 
/usr/local/var/run/openvswitch/vhost-user-1 created for vhost-user port 
vhost-user-1
2017-03-21T23:09:21.662Z|00105|bridge|INFO|bridge br0: added interface 
vhost-user-1 on port 6
.
.

darrell@---server125:~/ovs/ovs_master$ ll 
/usr/local/var/run/openvswitch/vhost-user-1
srwxr-xr-x 1 root root 0 Mar 21 16:30 
/usr/local/var/run/openvswitch/vhost-user-1=

However, I have the libvirt-qemu user, you seem to be missing; well, at least
based on the EAL logs.

darrell@ ---server125:~/ovs/ovs_master$ cat /etc/passwd | grep 
libvirt
libvirt-qemu:x:105:109:Libvirt Qemu,,,:/var/lib/libvirt:/bin/false

darrell@ ---server125:~/ovs/ovs_master$ groups libvirt-qemu
libvirt-qemu : kvm

darrell@ ---server125:~/ovs/ovs_master$ cat /etc/group | grep kvm
kvm:x:109:

Debug Log is 
here.

For past master (2 weeks ago and with -03/march=native compiler flags) OVS was 
trying to configure the socket owner as fdb/show.

DPDK Settings:

root@dpdk-compute0:/opt/build# ovs-vsctl --no-wait get Open_vSwitch . 
other_config
{dpdk-alloc-mem="2048", dpdk-extra="--vhost-owner libvirt-qemu:kvm --vhost-perm 
0666", dpdk-init="true", dpdk-lcore-mask="0x1", dpdk-socket-mem="1024,0"}

OVS config:

root@dpdk-compute0:/opt/build# ovs-vsctl show
972154fa-857e-45e8-b56b-77e5cb6eb685
Manager "ptcp:6640:127.0.0.1"
is_connected: true
Bridge br-int
Controller "tcp:127.0.0.1:6633"
is_connected: true
fail_mode: secure
Port int-br-ex
Interface int-br-ex
type: patch
options: {peer=phy-br-ex}
Port patch-tun
Interface patch-tun
type: patch
options: {peer=patch-int}
Port br-int
Interface br-int
type: internal
Bridge br-ex
Controller "tcp:127.0.0.1:6633"
is_connected: true
fail_mode: secure
Port "vhost-user-1"
Interface "vhost-user-1"
type: dpdkvhostuser
Port phy-br-ex
Interface phy-br-ex
type: patch
options: {peer=int-br-ex}
Port br-ex
Interface br-ex
type: internal
Port "intel_1g_1"
Interface "intel_1g_1"
type: dpdk
options: {dpdk-devargs=":06:00.1"}
Bridge br-tun
Controller "tcp:127.0.0.1:6633"
is_connected: true
fail_mode: secure
Port patch-int
Interface patch-int
type: patch
options: {peer=patch-tun}
Port br-tun
Interface br-tun
type: internal
ovs_version: "2.7.90"
root@dpdk-compute0:/opt/build#

Command for port add:

root@dpdk-compute0:/opt/build# ovs-vsctl add-port br-ex vhost-user-1 -- set 
Interface vhost-user-1 type=dpdkvhostuser

Actual socket rights after vhost create:

root@dpdk-compute0:/opt/build# ll /var/run/openvswitch/vhost-user-1
s- 1 root root 0 Mar 21 07:14 /var/run/openvswitch/vhost-user-1=

Why this happening? And one more question: can enable a debug logs for EAL over 
OVS?

Thanks for help.

--

Sincerely,

Aynur Shakirov, 27.

TIONIX RUS.

Planet Earth, Solar System, Milky Way.
___
discuss mailing list
disc...@openvswitch.org

Re: [ovs-discuss] OVS benchmark for kernel datapath module

2017-03-21 Thread Danish Sattar

Thanks for the information.

*Best Regards*
*Danish Sattar*

On Mon, Mar 20, 2017 at 1:26 PM, Vasmi Abidi  wrote:

>
> There are recordings of presentations about OVS performance at the OVS
> conference web page.
>
> For example: openvswitch.org/support/ovscon2015/17/1050-abidi.pptx
>
>
> - Vasmi
>
>
> --
> *From:* ovs-discuss-boun...@openvswitch.org  openvswitch.org> on behalf of Danish Sattar 
> *Sent:* Monday, March 20, 2017 9:50 AM
> *To:* ovs-discuss@openvswitch.org
> *Subject:* [ovs-discuss] OVS benchmark for kernel datapath module
>
> Hi everyone,
>
> I'm doing benchmark for the OVS kernel datapath module. i'm trying to see
> the effect of different packet sizes, data rates and hardware on the
> performance. i'm wondering if there are similar benchmarks available or if
> any relevant information is available.
>
> Thanks
> *Best Regards*
> *Danish Sattar*
>
___
discuss mailing list
disc...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-discuss

Re: [ovs-discuss] OVS-DPDK

2017-03-21 Thread Advith Nagappa

Hi Ian,

Yes, I am using OVS-2.6.1 release.

And yes, you are correct.

*ovs-vsctl add-port br0 dpdk-p1 -- set Interface dpdk-p1 type=dpdk*, infact
fails in 2.6.1;

whereas, *ovs-vsctl add-port br0 dpdk1 -- set Interface dpdk1 type=dpdk, *
succeeds.


As regards the use of



*options:dpdk-devargs=:00:0a.0*



It is only needed if you are using arbitrary port naming/hotplug support
which is included in OVS 2.7.0.

This answers my query.

But, If i may continue to ask a related query: from the dpdk log..

*2017-03-21T03:14:01Z|7|dpdk|INFO|EAL ARGS: ovs-vswitchd --socket-mem
1024,0 -c 0x0001*

*EAL: Detected 5 lcore(s)*

*EAL: Probing VFIO support...*

*EAL: WARNING: cpu flags constant_tsc=yes nonstop_tsc=no -> using
unreliable clock cycles !*

*EAL: PCI device :00:07.0 on NUMA socket -1*

*EAL:   probe driver: 8086:154c net_i40e_vf*

*EAL: PCI device :00:09.0 on NUMA socket -1*

*EAL:   probe driver: 8086:1572 net_i40e*

*PMD: eth_i40e_dev_init(): FW 5.0 API 1.5 NVM 05.00.02 eetrack 80002284*

*EAL: PCI device :00:0a.0 on NUMA socket -1*

*EAL:   probe driver: 8086:1572 net_i40e*

*PMD: eth_i40e_dev_init(): FW 5.0 API 1.5 NVM 05.00.02 eetrack 80002284*



Since I have done the binding 09.0 and 0a.0 to igb_uio driver, shouldn't we
see 'igb_uio' instead of 'net_i40e'?


Also, what is OVS-2.6.1's version on options:dpdk-devargs='', by that I
mean, how does the dpdk port know which interface should it bind to when
its not specified..


Best Regards

Advith Nagappa








On Mar 21, 2017 12:00 PM, "Stokes, Ian"  wrote:

> Apologies for top posting,
>
>
>
> Hi Advith, there seems to be a mismatch of OVS versions and expected
> features from the details you have provided.
>
>
>
> To confirm you are using OVS 2.6.1? Is there a specific commit ID you are
> using? Or are you using the 2.6.1 tag or release package?
>
>
>
> From the commands you have provided it looks like your trying to add dpdk
> ports with arbitrary names and PCI addresses.
>
>
>
> This is not possible in OVS 2.6.1, this ability was only added as of OVS
> 2.7.0.
>
>
>
> If you wanted to add 2 physical dpdk ports with 2.6.1 can you try the
> following
>
>
>
> ovs-vsctl add-port br0 dpdk0 -- set Interface dpdk0 type=dpdk
>
> ovs-vsctl add-port br0 dpdk1 -- set Interface dpdk1 type=dpdk
>
>
>
> Note the name of the dpdk port must start with dpdk followed by the number
> being added (starting at 0). This is a limitation that has since been
> removed in OVS 2.7.
>
>
>
> I’m surprised that you say you can use
>
>
>
> ovs-vsctl add-port br0 dpdk-p1 -- set Interface dpdk-p1 type=dpdk
>
>
>
> Testing OVS 2.6.1 tag on master with that command returned the vsctl error
>
>
>
> ovs-vsctl: Error detected while setting up 'dpdk-p1'.  See ovs-vswitchd
> log for details.
>
>
>
> for myself which would be expected.
>
>
>
> As regards the use of
>
>
>
> *options:dpdk-devargs=:00:0a.0*
>
>
>
> It is only needed if you are using arbitrary port naming/hotplug support
> which is included in OVS 2.7.0.
>
>
>
> If you can give these suggestions a shot it will help narrow down the
> issue at hand.
>
>
>
> Regards
>
> Ian
>
>
>
> *From:* ovs-discuss-boun...@openvswitch.org [mailto:ovs-discuss-bounces@op
> envswitch.org] *On Behalf Of *Advith Nagappa
> *Sent:* Tuesday, March 21, 2017 8:12 AM
> *To:* Darrell Ball 
> *Cc:* disc...@openvswitch.org
> *Subject:* Re: [ovs-discuss] OVS-DPDK
>
>
>
> I don’t see the pci memory mapping logs here.
>
> Can you also attach the full dpdk logs ?
>
>
>
> I have attached the dpdk-log.
>
>
>
> For PCI mapping, may below helps:
>
>
>
>
>
>
>
> *Bus info  Device  Class  Description*
>
> **
>
> *pci@:00:07.0   ens7network
>  XL710/X710 Virtual Function*
>
> *pci@:00:09.0   networkEthernet
> Controller X710 for 10GbE
>SFP+*
>
> *pci@:00:0a.0   networkEthernet
> Controller X710 for 10GbE
>   SFP+*
>
> * br0 networkEthernet
> interface*
>
> *ovs-netdev  networkEthernet interface*
>
>
>
> additionally,
>
>
>
> *Network devices using DPDK-compatible driver*
>
> **
>
> *:00:09.0 'Ethernet Controller X710 for 10GbE SFP+' drv=igb_uio
> unused=i40e*
>
> *:00:0a.0 'Ethernet Controller X710 for 10GbE SFP+' drv=igb_uio
> unused=i40e*
>
>
>
> *Network devices using kernel driver*
>
> *===*
>
> *:00:07.0 'XL710/X710 Virtual Function' if=ens7 drv=i40evf
> unused=igb_uio *Active**
>
>
>
> *Other network devices*
>
> *=*
>
> **
>
>
>
> *Crypto devices using DPDK-compatible driver*
>
> *===*
>
> **
>
>
>
> *Crypto devices using kernel driver*
>
>

Re: [ovs-discuss] RSTP for OVS in mininet

2017-03-21 Thread Joe Stringer

On 21 March 2017 at 13:43, Haitham Ghalwash  wrote:
> Hi all,
>
> I am trying to test RSTP on a mininet topology. when running
>
> sudo ovs-vsctl set Bridge s1 rstp_enable=true
>
> I am getting the following error
>
> ovs-vsctl: Bridge does not contain a column whose name matches "rstp_enable"
>
> the STP is running OK, but I am unable to set the RSTP.
>
> any suggestions?
>
> could the problem be due to the type of switch I am using? I tried both
> cls=OVSKernelSwitch and cls=OVSSwitch, while adding my switches.
>
> my OVS is version 2.0 which is installed by default with mininet 2.1.1

OVS 2.0 is ancient and does not include RSTP. You'll need to use newer OVS.
___
discuss mailing list
disc...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-discuss

[ovs-discuss] RSTP for OVS in mininet

2017-03-21 Thread Haitham Ghalwash

Hi all,

I am trying to test RSTP on a mininet topology. when running

sudo ovs-vsctl set Bridge s1 rstp_enable=true

I am getting the following error

ovs-vsctl: Bridge does not contain a column whose name matches "rstp_enable"

the STP is running OK, but I am unable to set the RSTP.

any suggestions?

could the problem be due to the type of switch I am using? I tried both 
cls=OVSKernelSwitch and cls=OVSSwitch, while adding my switches.

my OVS is version 2.0 which is installed by default with mininet 2.1.1



Best wishes,

Haitham Ghalwash

PhD. Student, UCONN




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

Re: [ovs-discuss] How does OVS learns the remote MACs

2017-03-21 Thread Ben Pfaff

On Tue, Mar 21, 2017 at 10:00:15AM -0700, Chris Mantis wrote:
> I think as OVS support OVSDB, it can learn the remote MACs from the OVSDB
> controller, but I guess this is not native support. If possible, can you
> provide an outline of how this control path can be supported natively? Can
> you elaborate what do you mean by "writing the flows"?
> 
> I am also looking for some overview of architecture of OVS. I found couple
> of videos online, but they are quite old. Simon Horman (2012), Michael
> Zayats (2015), Ben Pfaff (2013). Are there any meetup taking place for OVS?

We've got a day of talks at OpenStack Boston.  The schedule isn't posted
yet but here's some information:
https://www.openstack.org/summit/boston-2017/open-source-days/
___
discuss mailing list
disc...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-discuss

Re: [ovs-discuss] Reinstall OVS from git repo

2017-03-21 Thread Guru Shetty

On 21 March 2017 at 09:01, 蘇于倫  wrote:

> Hi everyone,
>
> I'd like to confirm which steps should I do to completely remove current
> OVS if I want to re-install OVS with modified C code in git repo ?
>
> Currently what my reinstall_ovs.sh does for old OVS removal is:
> sudo /usr/local/share/openvswitch/scripts/ovs-ctl stop
> sudo rm /usr/local/etc/openvswitch/conf.db
> ps aux | awk '/[o]vs-vswitchd/ {print $2}'
> rm -rf ovs/
>
> Are the steps above sufficient to completely remove OVS installation?
> After I run the re-install script, the code modification does not take
> effect. I modified in-band.c that output port of hidden flow is assigned
> to be the port number I want 0x1 for eth0. However, the hidden
> flows still show NORMAL action.
> Appreciate comments and suggestion!
>

Does 'find /usr -name ovs-vsctl' show 2 instances?


> thanks in advance
>
> Regards.
> Ethan
>
> ___
> 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] Reinstall OVS from git repo

2017-03-21 Thread 蘇于倫

Hi everyone,

I'd like to confirm which steps should I do to completely remove current
OVS if I want to re-install OVS with modified C code in git repo ?

Currently what my reinstall_ovs.sh does for old OVS removal is:
sudo /usr/local/share/openvswitch/scripts/ovs-ctl stop
sudo rm /usr/local/etc/openvswitch/conf.db
ps aux | awk '/[o]vs-vswitchd/ {print $2}'
rm -rf ovs/

Are the steps above sufficient to completely remove OVS installation?
After I run the re-install script, the code modification does not take
effect. I modified in-band.c that output port of hidden flow is assigned
to be the port number I want 0x1 for eth0. However, the hidden
flows still show NORMAL action.
Appreciate comments and suggestion!
thanks in advance

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

Re: [ovs-discuss] High Priority Traffic Path (dscp) for DPDK-OvS

2017-03-21 Thread Bodireddy, Bhanuprakash

>Hi all
>
>I need to specify a number of classes of service according to DSCP bits. Each
>class of service should be associated with a priority. For example: Packet A is
>sent with a DSCP value of 0 and packet B is sent with a value of 46; 0 has a
>lower priority than 46. Packet A arrives before packet B. If DPDK-OvS has been
>configured as such, Packet B will be transmitted before Packet A.
>
>I know that hardware switches have been designed to ensure certain classes
>of traffic can be scheduled ahead of other classes, also kernel mode OvS has
>the similar behavior coming from Linux kernel (tc, qdisk etc..). However, does
>DPDK-OvS have the same behavior? In master branch, I could not find any
>kind of scheduler to achieve this behavior.

OvS-DPDK in master doesn't prioritize packet based on PCP/DSCP fields. 

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

Re: [ovs-discuss] New dpif provider registration

2017-03-21 Thread Santhosh Alladi

Hi Ben,

Thank you for your reply.
We are offloading ovs functionalities to our hardware accelerator. 
We would like to know if there is any way to load shared libraries of our call 
backs, in the context of vswitchd? 

On Thu, Mar 16, 2017 at 12:34:59PM +, Santhosh Alladi wrote:
> We have written a new dpif provider class and registered it by adding 
> an entry to base_dpif_classes. Is it the correct way? If yes, can we 
> upstream it? If no,is there any other way to register an external 
> class?

Is your new provider of general interest?  Is it open source?  If so, we'd be 
happy to have an upstream contribution.

Otherwise, call dp_register_provider().
___
discuss mailing list
disc...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-discuss

[ovs-discuss] Relationship between struct flow and struct dp_packet_batch

2017-03-21 Thread Ali Volkan Atli

Hi

I have a question about the relationship between struct flow and struct 
dp_packet_batch. I can access multiple packets (inside dp_packet_batch) and 
only one flow (aux->flow) in dp_execute_cb(). It seems to me the packets in 
dp_packet_batch must be the same type (aux->flow->dl_type) or must be the same 
miniflow. Is that correct? Can I design upon this acceptance? Might there be 
any different type of packets in dp_execute_cb() coming from struct 
dp_packet_batch parameter?

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

Re: [ovs-discuss] OVS-DPDK

2017-03-21 Thread Stokes, Ian

Apologies for top posting,

Hi Advith, there seems to be a mismatch of OVS versions and expected features 
from the details you have provided.

To confirm you are using OVS 2.6.1? Is there a specific commit ID you are 
using? Or are you using the 2.6.1 tag or release package?

From the commands you have provided it looks like your trying to add dpdk ports 
with arbitrary names and PCI addresses.

This is not possible in OVS 2.6.1, this ability was only added as of OVS 2.7.0.

If you wanted to add 2 physical dpdk ports with 2.6.1 can you try the following

ovs-vsctl add-port br0 dpdk0 -- set Interface dpdk0 type=dpdk
ovs-vsctl add-port br0 dpdk1 -- set Interface dpdk1 type=dpdk

Note the name of the dpdk port must start with dpdk followed by the number 
being added (starting at 0). This is a limitation that has since been removed 
in OVS 2.7.

I’m surprised that you say you can use

ovs-vsctl add-port br0 dpdk-p1 -- set Interface dpdk-p1 type=dpdk

Testing OVS 2.6.1 tag on master with that command returned the vsctl error

ovs-vsctl: Error detected while setting up 'dpdk-p1'.  See ovs-vswitchd log for 
details.

for myself which would be expected.

As regards the use of

options:dpdk-devargs=:00:0a.0

It is only needed if you are using arbitrary port naming/hotplug support which 
is included in OVS 2.7.0.

If you can give these suggestions a shot it will help narrow down the issue at 
hand.

Regards
Ian

From: ovs-discuss-boun...@openvswitch.org 
[mailto:ovs-discuss-boun...@openvswitch.org] On Behalf Of Advith Nagappa
Sent: Tuesday, March 21, 2017 8:12 AM
To: Darrell Ball 
Cc: disc...@openvswitch.org
Subject: Re: [ovs-discuss] OVS-DPDK

I don’t see the pci memory mapping logs here.
Can you also attach the full dpdk logs ?

I have attached the dpdk-log.

For PCI mapping, may below helps:

Bus info  Device  Class  Description

pci@:00:07.0  ens7network
XL710/X710 Virtual Function
pci@:00:09.0  networkEthernet 
Controller X710 for 10GbE   
   SFP+
pci@:00:0a.0  networkEthernet 
Controller X710 for 10GbE   
  SFP+
 br0 networkEthernet interface
ovs-netdev  networkEthernet interface

additionally,

Network devices using DPDK-compatible driver

:00:09.0 'Ethernet Controller X710 for 10GbE SFP+' drv=igb_uio unused=i40e
:00:0a.0 'Ethernet Controller X710 for 10GbE SFP+' drv=igb_uio unused=i40e

Network devices using kernel driver
===
:00:07.0 'XL710/X710 Virtual Function' if=ens7 drv=i40evf unused=igb_uio 
*Active*

Other network devices
=

Crypto devices using DPDK-compatible driver
===

Crypto devices using kernel driver
==

Other crypto devices

What is your kernel and dpdk versions ?

Kernel - 4.4.0-66-generic
DPDK - 16.11.1

Can you share which portion of the following configuration you followed
http://docs.openvswitch.org/en/latest/intro/install/dpdk/

Install DPDK - used 1 and 3 (avoided shared lib config)

Install OVS  - As IS

Hugepages - used 1 G huge page. Passed "default_hugepagesz=1G hugepagesz=1G 
hugepages=1" as boot time parameter.

grep -i huge /proc/meminfo
AnonHugePages: 14336 kB
HugePages_Total:   5
HugePages_Free:4
HugePages_Rsvd:0
HugePages_Surp:0
Hugepagesize:1048576 kB

VFIO : Did not use Vfio. Used Igb_uio.

Setup OVS: As is. Did not specify pmd-cpu-mask.
Validating: As is, with the :00:09.0 and :00:0a.0 as device address. 
Fails.

Appreciate your inputs. Look forward to your response.

Best Regards
Advith

On Tue, Mar 21, 2017 at 7:50 AM, Darrell Ball 
> wrote:

From: Darrell Ball >
Date: Monday, March 20, 2017 at 10:12 PM
To: Advith Nagappa >, 
Ben Pfaff >
Cc: "disc...@openvswitch.org" 
>
Subject: Re: [ovs-discuss] OVS-DPDK

From: 
>
 on behalf of Advith Nagappa 
>
Date: Monday, March 20, 2017 at 8:19 PM
To: Ben Pfaff >
Cc: "disc...@openvswitch.org" 
>
Subject: Re: [ovs-discuss]

Re: [ovs-discuss] OVS-DPDK

2017-03-21 Thread Advith Nagappa

I don’t see the pci memory mapping logs here.

Can you also attach the full dpdk logs ?

I have attached the dpdk-log.

For PCI mapping, may below helps:



*Bus info  Device  Class  Description*
**
*pci@:00:07.0  ens7networkXL710/X710 Virtual Function*
*pci@:00:09.0  networkEthernet Controller X710 for
10GbE  SFP+*
*pci@:00:0a.0  networkEthernet Controller X710 for
10GbE SFP+*
* br0 networkEthernet
interface*
*ovs-netdev  networkEthernet interface*

additionally,

*Network devices using DPDK-compatible driver*
**
*:00:09.0 'Ethernet Controller X710 for 10GbE SFP+' drv=igb_uio
unused=i40e*
*:00:0a.0 'Ethernet Controller X710 for 10GbE SFP+' drv=igb_uio
unused=i40e*

*Network devices using kernel driver*
*===*
*:00:07.0 'XL710/X710 Virtual Function' if=ens7 drv=i40evf
unused=igb_uio *Active**

*Other network devices*
*=*
**

*Crypto devices using DPDK-compatible driver*
*===*
**

*Crypto devices using kernel driver*
*==*
**

*Other crypto devices*
**
**



What is your kernel and dpdk versions ?

Kernel - 4.4.0-66-generic
DPDK - 16.11.1


Can you share which portion of the following configuration you followed

http://docs.openvswitch.org/en/latest/intro/install/dpdk/



Install *DPDK *- used 1 and 3 (avoided shared lib config)

Install *OVS  *- As IS

*Hugepages *- used 1 G huge page. Passed "default_hugepagesz=1G
hugepagesz=1G hugepages=1" as boot time parameter.

*grep -i huge /proc/meminfo*
*AnonHugePages: 14336 kB*
*HugePages_Total:   5*
*HugePages_Free:4*
*HugePages_Rsvd:0*
*HugePages_Surp:0*
*Hugepagesize:1048576 kB*


*VFIO : *Did not use Vfio. Used Igb_uio.

Setup OVS: As is. Did not specify pmd-cpu-mask.
*Validating*: As is, with the :00:09.0 and :00:0a.0 as device
address. Fails.




Appreciate your inputs. Look forward to your response.

Best Regards
Advith

On Tue, Mar 21, 2017 at 7:50 AM, Darrell Ball  wrote:

>
>
>
>
> *From: *Darrell Ball 
> *Date: *Monday, March 20, 2017 at 10:12 PM
> *To: *Advith Nagappa , Ben Pfaff 
> *Cc: *"disc...@openvswitch.org" 
> *Subject: *Re: [ovs-discuss] OVS-DPDK
>
>
>
>
>
>
>
> *From: * on behalf of Advith Nagappa
> 
> *Date: *Monday, March 20, 2017 at 8:19 PM
> *To: *Ben Pfaff 
> *Cc: *"disc...@openvswitch.org" 
> *Subject: *Re: [ovs-discuss] OVS-DPDK
>
>
>
> It did not tell me anything:
>
>
>
> *Mar 20 11:42:23  ovs-vsctl: ovs|1|vsctl|INFO|Called as ovs-vsctl
> add-port br0 dpdk-p0 -- set Interface dpdk-p0 type=dpdk
> options:dpdk-devargs=:00:0a.0*
>
> *Mar 20 11:42:23  ovs-vswitchd[23906]: ovs|00042|bridge|WARN|could not
> open network device dpdk-p0 (No such device)*
>
> *Mar 20 11:42:23  ovs-vswitchd[23906]: ovs|00044|bridge|WARN|could not
> open network device dpdk-p0 (No such device)*
>
>
>
>
>
> A ./dpdk-devbind.py --status shows the below results, confirming device
> binding
>
>
>
> *Network devices using DPDK-compatible driver*
>
> **
>
> *:00:09.0 'Ethernet Controller X710 for 10GbE SFP+' drv=igb_uio
> unused=i40e*
>
> *:00:0a.0 'Ethernet Controller X710 for 10GbE SFP+' drv=igb_uio
> unused=i40e*
>
>
>
>
>
>
>
> *Network devices using kernel driver*
>
> *===*
>
> *:00:07.0 'XL710/X710 Virtual Function' if=ens7 drv=i40evf
> unused=igb_uio *Active**
>
>
>
> *Other network devices*
>
> *=*
>
> **
>
>
>
> *Crypto devices using DPDK-compatible driver*
>
> *===*
>
> **
>
>
>
> *Crypto devices using kernel driver*
>
> *==*
>
> **
>
>
>
> *Other crypto devices*
>
> **
>
> **
>
>
>
> But, I did notice a curious thing:
>
>
>
> when I init OVS with dpdk, using:
>
>
>
> ovs-vsctl --no-wait set Open_vSwitch . other_config:dpdk-init=true
>
> ovs-vsctl --no-wait set Open_vSwitch . other_config:dpdk-socket-mem="
> 1024,0"
>
>
>
>
>
>
>
>
>
> *2017-03-21T03:14:01Z|7|dpdk|INFO|EAL ARGS: ovs-vswitchd --socket-mem
> 1024,0 -c 0x0001*
>
> *EAL: Detected 5 lcore(s)*
>
> *EAL: Probing VFIO support...*
>
> *EAL: WARNING: cpu flags constant_tsc=yes nonstop_tsc=no -> using
> unreliable clock cycles !*
>
> *EAL: PCI device :00:07.0 on NUMA socket -1*
>
> *EAL:   probe

Re: [ovs-discuss] High Priority Traffic Path (dscp) for DPDK-OvS

2017-03-21 Thread Darrell Ball

That’s right; that is what I meant by “this is yet even further away from your 
needs”

On 3/20/17, 11:50 PM, "Ali Volkan Atli"  wrote:


I know ingress/egress policier but they cannot give me traffic 
prioritization, right? 

- Volkan

From: Darrell Ball [db...@vmware.com]
Sent: Tuesday, March 21, 2017 9:43 AM
To: Ali Volkan Atli; disc...@openvswitch.org
Subject: Re: [ovs-discuss] High Priority Traffic Path (dscp) for DPDK-OvS

For completeness
There is also ingress side policing for DPDK support, but this is yet even 
further away from your needs

On 3/20/17, 11:08 PM, "ovs-discuss-boun...@openvswitch.org on behalf of 
Darrell Ball"  wrote:

Afaik
OVS-DPDK only supports egress-policing qos

https://urldefense.proofpoint.com/v2/url?u=http-3A__openvswitch.org_support_dist-2Ddocs_ovs-2Dvswitchd.conf.db.5.pdf=DwICAg=uilaK90D4TOVoH58JNXRgQ=BVhFA09CGX7JQ5Ih-uZnsw=RIWw06JUXu6nQ6rBtMjodUMOfYzlTQWCpl3cvhBcMqQ=dEB0J4ZNbb6D3fyTCQtQSOL4ESw61sttj73HOUu81OI=
see egress--policer

On 3/20/17, 10:30 PM, "ovs-discuss-boun...@openvswitch.org on behalf of 
Ali Volkan Atli"  wrote:


Hi all

I need to specify a number of classes of service according to DSCP 
bits. Each class of service should be associated with a priority. For example: 
Packet A is sent with a DSCP value of 0 and packet B is sent with a value of 
46; 0 has a lower priority than 46. Packet A arrives before packet B. If 
DPDK-OvS has been configured as such, Packet B will be transmitted before 
Packet A.

I know that hardware switches have been designed to ensure certain 
classes of traffic can be scheduled ahead of other classes, also kernel mode 
OvS has the similar behavior coming from Linux kernel (tc, qdisk etc..). 
However, does DPDK-OvS have the same behavior? In master branch, I could not 
find any kind of scheduler to achieve this behavior.

Thanks in advance..

- Volkan
___
discuss mailing list
disc...@openvswitch.org

https://urldefense.proofpoint.com/v2/url?u=https-3A__mail.openvswitch.org_mailman_listinfo_ovs-2Ddiscuss=DwICAg=uilaK90D4TOVoH58JNXRgQ=BVhFA09CGX7JQ5Ih-uZnsw=t_URk5HzgDgCEYW7ckfF7YlE3wYVnLqEFyHzFpjEWXk=OyfZtaFWTFg_JXtm1LpO0IIaABYbz8EWtKp3NZ7amGE=


___
discuss mailing list
disc...@openvswitch.org

https://urldefense.proofpoint.com/v2/url?u=https-3A__mail.openvswitch.org_mailman_listinfo_ovs-2Ddiscuss=DwICAg=uilaK90D4TOVoH58JNXRgQ=BVhFA09CGX7JQ5Ih-uZnsw=RIWw06JUXu6nQ6rBtMjodUMOfYzlTQWCpl3cvhBcMqQ=KZd3tmsCEFpyjf2b4rRZRTqJmQaeFDy8dK0Xvrggjdo=




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

Re: [ovs-discuss] OVS-DPDK

2017-03-21 Thread Darrell Ball



From: Darrell Ball 
Date: Monday, March 20, 2017 at 10:12 PM
To: Advith Nagappa , Ben Pfaff 
Cc: "disc...@openvswitch.org" 
Subject: Re: [ovs-discuss] OVS-DPDK



From:  on behalf of Advith Nagappa 

Date: Monday, March 20, 2017 at 8:19 PM
To: Ben Pfaff 
Cc: "disc...@openvswitch.org" 
Subject: Re: [ovs-discuss] OVS-DPDK

It did not tell me anything:

Mar 20 11:42:23  ovs-vsctl: ovs|1|vsctl|INFO|Called as ovs-vsctl add-port 
br0 dpdk-p0 -- set Interface dpdk-p0 type=dpdk options:dpdk-devargs=:00:0a.0
Mar 20 11:42:23  ovs-vswitchd[23906]: ovs|00042|bridge|WARN|could not open 
network device dpdk-p0 (No such device)
Mar 20 11:42:23  ovs-vswitchd[23906]: ovs|00044|bridge|WARN|could not open 
network device dpdk-p0 (No such device)


A ./dpdk-devbind.py --status shows the below results, confirming device binding

Network devices using DPDK-compatible driver

:00:09.0 'Ethernet Controller X710 for 10GbE SFP+' drv=igb_uio unused=i40e
:00:0a.0 'Ethernet Controller X710 for 10GbE SFP+' drv=igb_uio unused=i40e



Network devices using kernel driver
===
:00:07.0 'XL710/X710 Virtual Function' if=ens7 drv=i40evf unused=igb_uio 
*Active*

Other network devices
=


Crypto devices using DPDK-compatible driver
===


Crypto devices using kernel driver
==


Other crypto devices



But, I did notice a curious thing:

when I init OVS with dpdk, using:

ovs-vsctl --no-wait set Open_vSwitch . other_config:dpdk-init=true
ovs-vsctl --no-wait set Open_vSwitch . other_config:dpdk-socket-mem="1024,0"




2017-03-21T03:14:01Z|7|dpdk|INFO|EAL ARGS: ovs-vswitchd --socket-mem 1024,0 
-c 0x0001
EAL: Detected 5 lcore(s)
EAL: Probing VFIO support...
EAL: WARNING: cpu flags constant_tsc=yes nonstop_tsc=no -> using unreliable 
clock cycles !
EAL: PCI device :00:07.0 on NUMA socket -1
EAL:   probe driver: 8086:154c net_i40e_vf
EAL: PCI device :00:09.0 on NUMA socket -1
EAL:   probe driver: 8086:1572 net_i40e
PMD: eth_i40e_dev_init(): FW 5.0 API 1.5 NVM 05.00.02 eetrack 80002284
EAL: PCI device :00:0a.0 on NUMA socket -1
EAL:   probe driver: 8086:1572 net_i40e
PMD: eth_i40e_dev_init(): FW 5.0 API 1.5 NVM 05.00.02 eetrack 80002284

I don’t see the pci memory mapping logs here.
Can you also attach the full dpdk logs ?
What is your kernel and dpdk versions ?
Can you share which portion of the following configuration you followed
http://docs.openvswitch.org/en/latest/intro/install/dpdk/



I was wondering if the probe driver for 09.0 and 0a.0 should have been 
something like 'igb_uio'.. I am not sure if this is how it should be?

Appreciate your inputs.

Best Regards
Advith Nagappa

On Tue, Mar 21, 2017 at 3:33 AM, Ben Pfaff > 
wrote:
On Tue, Mar 21, 2017 at 02:36:23AM +0100, Advith Nagappa wrote:
> Hi,
>
> I have DPDK 16.11.1 and OVS 2.6.1, with 1 Gb Huge page/ and 2 NICs bound
> with Igb_uio drivers.
>
> I run in to trouble while creating DPDK ports on the OVS bridge.
>
>
> *ovs-vsctl add-port br0 dpdk-p1 -- set Interface dpdk-p1 type=dpdk*
>
> works perfectly fine.
>
> But,
>
> *ovs-vsctl add-port br0 dpdk-p0 -- set Interface dpdk-p0 type=dpdk
> options:dpdk-devargs=:00:0a.0*
>
> gives an error:
> ovs-vsctl: Error detected while setting up 'dpdk-p0'.  See ovs-vswitchd log
> for details.

What's in the log?

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

Re: [ovs-discuss] High Priority Traffic Path (dscp) for DPDK-OvS

2017-03-21 Thread Ali Volkan Atli

I know ingress/egress policier but they cannot give me traffic prioritization, 
right? 

- Volkan

From: Darrell Ball [db...@vmware.com]
Sent: Tuesday, March 21, 2017 9:43 AM
To: Ali Volkan Atli; disc...@openvswitch.org
Subject: Re: [ovs-discuss] High Priority Traffic Path (dscp) for DPDK-OvS

For completeness
There is also ingress side policing for DPDK support, but this is yet even 
further away from your needs

On 3/20/17, 11:08 PM, "ovs-discuss-boun...@openvswitch.org on behalf of Darrell 
Ball"  wrote:

Afaik
OVS-DPDK only supports egress-policing qos

https://urldefense.proofpoint.com/v2/url?u=http-3A__openvswitch.org_support_dist-2Ddocs_ovs-2Dvswitchd.conf.db.5.pdf=DwICAg=uilaK90D4TOVoH58JNXRgQ=BVhFA09CGX7JQ5Ih-uZnsw=RIWw06JUXu6nQ6rBtMjodUMOfYzlTQWCpl3cvhBcMqQ=dEB0J4ZNbb6D3fyTCQtQSOL4ESw61sttj73HOUu81OI=
see egress--policer

On 3/20/17, 10:30 PM, "ovs-discuss-boun...@openvswitch.org on behalf of Ali 
Volkan Atli"  wrote:

Hi all

I need to specify a number of classes of service according to DSCP 
bits. Each class of service should be associated with a priority. For example: 
Packet A is sent with a DSCP value of 0 and packet B is sent with a value of 
46; 0 has a lower priority than 46. Packet A arrives before packet B. If 
DPDK-OvS has been configured as such, Packet B will be transmitted before 
Packet A.

I know that hardware switches have been designed to ensure certain 
classes of traffic can be scheduled ahead of other classes, also kernel mode 
OvS has the similar behavior coming from Linux kernel (tc, qdisk etc..). 
However, does DPDK-OvS have the same behavior? In master branch, I could not 
find any kind of scheduler to achieve this behavior.

Thanks in advance..

- Volkan
___
discuss mailing list
disc...@openvswitch.org

https://urldefense.proofpoint.com/v2/url?u=https-3A__mail.openvswitch.org_mailman_listinfo_ovs-2Ddiscuss=DwICAg=uilaK90D4TOVoH58JNXRgQ=BVhFA09CGX7JQ5Ih-uZnsw=t_URk5HzgDgCEYW7ckfF7YlE3wYVnLqEFyHzFpjEWXk=OyfZtaFWTFg_JXtm1LpO0IIaABYbz8EWtKp3NZ7amGE=

___
discuss mailing list
disc...@openvswitch.org

https://urldefense.proofpoint.com/v2/url?u=https-3A__mail.openvswitch.org_mailman_listinfo_ovs-2Ddiscuss=DwICAg=uilaK90D4TOVoH58JNXRgQ=BVhFA09CGX7JQ5Ih-uZnsw=RIWw06JUXu6nQ6rBtMjodUMOfYzlTQWCpl3cvhBcMqQ=KZd3tmsCEFpyjf2b4rRZRTqJmQaeFDy8dK0Xvrggjdo=

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

Re: [ovs-discuss] High Priority Traffic Path (dscp) for DPDK-OvS

2017-03-21 Thread Darrell Ball

For completeness
There is also ingress side policing for DPDK support, but this is yet even 
further away from your needs

On 3/20/17, 11:08 PM, "ovs-discuss-boun...@openvswitch.org on behalf of Darrell 
Ball"  wrote:

Afaik
OVS-DPDK only supports egress-policing qos

https://urldefense.proofpoint.com/v2/url?u=http-3A__openvswitch.org_support_dist-2Ddocs_ovs-2Dvswitchd.conf.db.5.pdf=DwICAg=uilaK90D4TOVoH58JNXRgQ=BVhFA09CGX7JQ5Ih-uZnsw=RIWw06JUXu6nQ6rBtMjodUMOfYzlTQWCpl3cvhBcMqQ=dEB0J4ZNbb6D3fyTCQtQSOL4ESw61sttj73HOUu81OI=
 
see egress--policer

On 3/20/17, 10:30 PM, "ovs-discuss-boun...@openvswitch.org on behalf of Ali 
Volkan Atli"  wrote:


Hi all

I need to specify a number of classes of service according to DSCP 
bits. Each class of service should be associated with a priority. For example: 
Packet A is sent with a DSCP value of 0 and packet B is sent with a value of 
46; 0 has a lower priority than 46. Packet A arrives before packet B. If 
DPDK-OvS has been configured as such, Packet B will be transmitted before 
Packet A.

I know that hardware switches have been designed to ensure certain 
classes of traffic can be scheduled ahead of other classes, also kernel mode 
OvS has the similar behavior coming from Linux kernel (tc, qdisk etc..). 
However, does DPDK-OvS have the same behavior? In master branch, I could not 
find any kind of scheduler to achieve this behavior. 

Thanks in advance..

- Volkan
___
discuss mailing list
disc...@openvswitch.org

https://urldefense.proofpoint.com/v2/url?u=https-3A__mail.openvswitch.org_mailman_listinfo_ovs-2Ddiscuss=DwICAg=uilaK90D4TOVoH58JNXRgQ=BVhFA09CGX7JQ5Ih-uZnsw=t_URk5HzgDgCEYW7ckfF7YlE3wYVnLqEFyHzFpjEWXk=OyfZtaFWTFg_JXtm1LpO0IIaABYbz8EWtKp3NZ7amGE=
 


___
discuss mailing list
disc...@openvswitch.org

https://urldefense.proofpoint.com/v2/url?u=https-3A__mail.openvswitch.org_mailman_listinfo_ovs-2Ddiscuss=DwICAg=uilaK90D4TOVoH58JNXRgQ=BVhFA09CGX7JQ5Ih-uZnsw=RIWw06JUXu6nQ6rBtMjodUMOfYzlTQWCpl3cvhBcMqQ=KZd3tmsCEFpyjf2b4rRZRTqJmQaeFDy8dK0Xvrggjdo=
 


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

Re: [ovs-discuss] High Priority Traffic Path (dscp) for DPDK-OvS

2017-03-21 Thread Darrell Ball

Afaik
OVS-DPDK only supports egress-policing qos
http://openvswitch.org/support/dist-docs/ovs-vswitchd.conf.db.5.pdf
see egress--policer

On 3/20/17, 10:30 PM, "ovs-discuss-boun...@openvswitch.org on behalf of Ali 
Volkan Atli"  wrote:


Hi all

I need to specify a number of classes of service according to DSCP bits. 
Each class of service should be associated with a priority. For example: Packet 
A is sent with a DSCP value of 0 and packet B is sent with a value of 46; 0 has 
a lower priority than 46. Packet A arrives before packet B. If DPDK-OvS has 
been configured as such, Packet B will be transmitted before Packet A.

I know that hardware switches have been designed to ensure certain classes 
of traffic can be scheduled ahead of other classes, also kernel mode OvS has 
the similar behavior coming from Linux kernel (tc, qdisk etc..). However, does 
DPDK-OvS have the same behavior? In master branch, I could not find any kind of 
scheduler to achieve this behavior. 

Thanks in advance..

- Volkan
___
discuss mailing list
disc...@openvswitch.org

https://urldefense.proofpoint.com/v2/url?u=https-3A__mail.openvswitch.org_mailman_listinfo_ovs-2Ddiscuss=DwICAg=uilaK90D4TOVoH58JNXRgQ=BVhFA09CGX7JQ5Ih-uZnsw=t_URk5HzgDgCEYW7ckfF7YlE3wYVnLqEFyHzFpjEWXk=OyfZtaFWTFg_JXtm1LpO0IIaABYbz8EWtKp3NZ7amGE=
 


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

Re: [ovs-discuss] OVS-DPDK

Re: [ovs-discuss] Reinstall OVS from git repo

Re: [ovs-discuss] OVS+DPDK: socket permissions' problem

Re: [ovs-discuss] OVS benchmark for kernel datapath module

Re: [ovs-discuss] OVS-DPDK

Re: [ovs-discuss] RSTP for OVS in mininet

[ovs-discuss] RSTP for OVS in mininet

Re: [ovs-discuss] How does OVS learns the remote MACs

Re: [ovs-discuss] Reinstall OVS from git repo

[ovs-discuss] Reinstall OVS from git repo

Re: [ovs-discuss] High Priority Traffic Path (dscp) for DPDK-OvS

Re: [ovs-discuss] New dpif provider registration

[ovs-discuss] Relationship between struct flow and struct dp_packet_batch

Re: [ovs-discuss] OVS-DPDK

Re: [ovs-discuss] OVS-DPDK

Re: [ovs-discuss] High Priority Traffic Path (dscp) for DPDK-OvS

Re: [ovs-discuss] OVS-DPDK

Re: [ovs-discuss] High Priority Traffic Path (dscp) for DPDK-OvS

Re: [ovs-discuss] High Priority Traffic Path (dscp) for DPDK-OvS

Re: [ovs-discuss] High Priority Traffic Path (dscp) for DPDK-OvS

20 matches

Site Navigation

Mail list logo

Footer information