[ovs-dev] The bug of slflow and upcall

We meet a problem with sflow enable. The packet miss upcall to vswitchd has a 1 second lagency. The reason is sflow will get interface stats from kernel use the method of rtnetlink,and the rtnetlink will wait the rtln_lock. also this thread will hold the global mutex of sflow moudle. at this time

Re: [ovs-dev] Delete Flows matching specific cookie - OpenFlow 1.3.5 Spec support by OpenVSwitch

On 4/23/18, 6:53 PM, "Carlos Ferreira" wrote: @IWAMOTO Hello IWAMOTO, No, I do not get any kind of error from Ryu. I have also verified the structure of the Openflow messages sent to the switch using Wireshark and no anomalies were found. The

[ovs-dev] [PATCH] poc: Automate building of Fedora rpm packages

This patch automates building of Fedora rpm packages (Just like we are already doing this for for CentOS and Ubuntu). Signed-off-by: Ansis Atteka --- poc/builders/Vagrantfile| 12 + poc/playbook-fedora-builder.yml | 117 2

[ovs-dev] interface mac setting

One question, why now ovs can only set the mac of internal interface, for example: ovs-vsctl set Interface p1 type=internal mac=\"00:11:22:33:44:55\" ovs-vsctl get Interface p1 mac_in_use And the doc about 'mac' is not explained, why we cannot set it for other type interface. So it's a bug?

Re: [ovs-dev] Delete Flows matching specific cookie - OpenFlow 1.3.5 Spec support by OpenVSwitch

@IWAMOTO Hello IWAMOTO, No, I do not get any kind of error from Ryu. I have also verified the structure of the Openflow messages sent to the switch using Wireshark and no anomalies were found. The packet was well structured. @Darrell, Darrel, thank you for the info. I tried to use the del-flows

Re: [ovs-dev] Delete Flows matching specific cookie - OpenFlow 1.3.5 Spec support by OpenVSwitch

//You can verify that OVS supports deletion by cookie specification by checking these tests: 932: ofproto.at:1746ofproto - del flows based on cookie 933: ofproto.at:1767ofproto - del flows based on cookie mask // Run the tests using “make check” like this: sudo make check

Re: [ovs-dev] Delete Flows matching specific cookie - OpenFlow 1.3.5 Spec support by OpenVSwitch

On Tue, 24 Apr 2018 08:16:45 +0900, Carlos Ferreira wrote: > > Hello to all > > According to the OpenFlow 1.3.5 spec, page 44 specifies the following: > > > "Modify and delete commands can also be filtered by cookie value, if > the cookie_mask field contains > a value other than 0. This

[ovs-dev] Delete Flows matching specific cookie - OpenFlow 1.3.5 Spec support by OpenVSwitch

Hello to all According to the OpenFlow 1.3.5 spec, page 44 specifies the following: "Modify and delete commands can also be filtered by cookie value, if the cookie_mask field contains a value other than 0. This constraint is that the bits specified by the cookie_mask in both the cookie field of

Re: [ovs-dev] [PATCH V2] datapath: Prevent panic

On Tue, Apr 17, 2018 at 12:34 PM, Greg Rose wrote: > On RHEL 7.x kernels we observe a panic induced by a paging error > when the timer kicks off a job that subsequently accesses memory > that belonged to the openvswitch kernel module but was since > unloaded - thus the

Re: [ovs-dev] [PATCH V2] datapath: Prevent panic

On Fri, Apr 20, 2018 at 09:03:14AM -0700, Gregory Rose wrote: > On 4/20/2018 5:39 AM, Eric Garver wrote: > > On Thu, Apr 19, 2018 at 08:07:33PM -0700, Gregory Rose wrote: > > Fantastic, I'll test this and whip up a patch. > > > Thanks! > > > > > > - Greg > > I'll be on the lookout for it. Thanks.

Re: [ovs-dev] [PATCH V2] datapath: Prevent panic

On 4/23/2018 9:19 AM, Gregory Rose wrote: On 4/20/2018 9:36 AM, Gregory Rose wrote: On 4/20/2018 9:03 AM, Gregory Rose wrote: On 4/20/2018 5:39 AM, Eric Garver wrote: On Thu, Apr 19, 2018 at 08:07:33PM -0700, Gregory Rose wrote: Fantastic, I'll test this and whip up a patch. Thanks! -

Re: [ovs-dev] [PATCH V2] datapath: Prevent panic

On 4/20/2018 9:36 AM, Gregory Rose wrote: On 4/20/2018 9:03 AM, Gregory Rose wrote: On 4/20/2018 5:39 AM, Eric Garver wrote: On Thu, Apr 19, 2018 at 08:07:33PM -0700, Gregory Rose wrote: Fantastic, I'll test this and whip up a patch. Thanks! - Greg I'll be on the lookout for it. Thanks.

[ovs-dev] Redes Sociales - Webinar

Reclutamiento y contratación por generación Mayo 08 - webinar Interactivo Objetivo: Objetivos del Webinar - Aplicar el Reclutamiento y Selección de acuerdo con cada generación - Aplicar la tecnología en el proceso de atracción de talento, haciéndolo más efectivo. - Conocerá las

[ovs-dev] [branch-2.7 PATCH] dpdk: Use DPDK 16.11.6 release.

Modify travis linux build script to use the latest DPDK stable release 16.11.6. Update docs for latest DPDK stable releases. Signed-off-by: Kevin Traynor --- .travis/linux-build.sh | 2 +- Documentation/faq/releases.rst | 2 +-

[ovs-dev] Open stack/AWS/Cloud Stack Users Contact

Hi, We are glad to inform you about our recent list release of Open stack/AWS/Cloud Stack Users Contact List and we are know to learn your interest in acquiring the list. We Have Other Competitors also like: Amazon S3, Microsoft Azure, Verizon Cloud, Profit Bricks, Open Nebula, Cisco Cloud

[ovs-dev] [ PATCH v2] dpdk: Use DPDK 17.11.2 release.

Modify travis linux build script to use the latest DPDK stable release 17.11.2. Update docs for latest DPDK stable releases. Signed-off-by: Kevin Traynor --- .travis/linux-build.sh | 2 +- Documentation/faq/releases.rst | 4 ++--

[ovs-dev] [PATCH] dpdk: Use DPDK 17.11.2 release.

Modify docs and travis linux build script to use the latest DPDK stable release 17.11.2. Signed-off-by: Kevin Traynor --- .travis/linux-build.sh | 2 +- Documentation/faq/releases.rst | 2 +- Documentation/intro/install/dpdk.rst | 8

Re: [ovs-dev] [PATCH] OVN: show gw chassis in decreasing prio order

Actually, let me add on that this seems like a good candidate for a new test to be added. On 04/23/2018 09:39 AM, Mark Michelson wrote: Nice job! Acked-by: Mark Michelson On 04/20/2018 12:46 PM, Lorenzo Bianconi wrote: Report gateway chassis in decreasing priority

Re: [ovs-dev] [PATCH] OVN: show gw chassis in decreasing prio order

Nice job! Acked-by: Mark Michelson On 04/20/2018 12:46 PM, Lorenzo Bianconi wrote: Report gateway chassis in decreasing priority order running ovn-nbctl show sub-command. Add get_ordered_gw_chassis_prio_list routine to sort gw chassis according to the configured priority

[ovs-dev] photos for your company

I wanted to follow up from last week. We provide image editing like – photos cutting out and retouching. We assure you the top quality. We provide below image editing services : Clipping path Image cut out Image shadow creation Image masking Photo retouching Beauty retouching - (skin, face,

[ovs-dev] [PATCH v7] Configurable Link State Change (LSC) detection mode

It is possible to set LSC detection mode to polling or interrupt mode for DPDK interfaces. The default is polling mode. To set interrupt mode, option dpdk-lsc-interrupt has to be set to true. For detailed description and usage see the dpdk install documentation. Signed-off-by: Robert Mulik

Re: [ovs-dev] [PATCH] tests: Fix ovn test failures in sandbox test env.

On Sun, Apr 22, 2018 at 9:53 AM, Han Zhou wrote: > When clustering support is introduced, the naming convention of > environment variables OVN_NB_DB and OVN_SB_DB changed (something > like unix:nb1.ovsdb). This leads to all ovn-nbctl test cases and > many others fail when they

Re: [ovs-dev] raft ovsdb clustering with scale test

Hi : I was able to go little further from log perspective with debug level and see proper error: However there were couple of changes that I did for current setup. For controllers setup, since I am using 3 vms, to keep the specs in line with current ovn scale env: 1. Increased the virtual

Re: [ovs-dev] [PATCH 1/2] ovn: Support port groups in ACLs

Wow great job Han! I'll take a look ASAP, this is really useful indeed. Thanks! Daniel On Sun, Apr 22, 2018 at 7:17 PM, Han Zhou wrote: > > > On Fri, Mar 2, 2018 at 7:26 AM, Guru Shetty wrote: > > > > > > > > On 1 March 2018 at 15:43, Han Zhou

[ovs-dev] Upper limit of QoS burst

Hi: I found that in struct ofputil_meter_band, rate and burst are all 32 bits, the max burst is: for bandwidth: 4GB = 32Gb for pps: 4G packets/1000 = 4M packets In our high performance setup, 4M packets burst is easily achievable, so I suggest change these variable to uint64_t