On Thu, Feb 08, 2018 at 05:17:56AM +0800, Gregory Rose wrote:
> On 2/7/2018 10:46 AM, Ben Pfaff wrote:
> > On Fri, Feb 02, 2018 at 10:23:04AM -0800, Gregory Rose wrote:
> >> On 1/31/2018 5:53 AM, Yi Yang wrote:
> >>> v1->v2
> >>> - Fix compilation error in linux-3.10.107
> >>>
> >>> This patch se
This commit manually reverts the current per port mempool model to the
previous shared mempool model for DPDK ports.
OVS previously used a shared mempool model for ports with the same MTU
configuration. This was replaced by a per port mempool model to address
issues flagged by users such as:
http
> Hi all,
>
> As discussed on the OVS-DPDK community call, I've manually reverted the per
> port mempool changes in OVS-DPDK on a branch on my own git hub. This had to
> be re-introduced manually due to the number of commits and work that had went
> on top of the per port implementation.
>
> F
Hello my good friend
Good day and how are you today? Hope all is well with you and your family? I am
using this opportunity to inform you that this multi- million-dollar business
has been concluded with the assistance of another partner from India who
financed the transaction to a logical con
Hi Ilya,
Yes, that was the consensus yesterday in the OVS-DPDK call: Revert to the
legacy shared mempool for the 2.9 branch only prior to OVS 2.9.0 release to
avoid all issues with upgrades to 2.9 and compatibility complications when
backporting shared mempool to the 2.9 branch post the release
On 02/08/2018 01:56 PM, Jan Scheurich wrote:
> Hi Ilya,
>
> Yes, that was the consensus yesterday in the OVS-DPDK call: Revert to the
> legacy shared mempool for the 2.9 branch only prior to OVS 2.9.0 release to
> avoid all issues with upgrades to 2.9 and compatibility complications when
> back
> -Original Message-
> From: Ilya Maximets [mailto:i.maxim...@samsung.com]
> Sent: Thursday, February 8, 2018 12:19 PM
> To: ovs-dev@openvswitch.org; Stokes, Ian
> Cc: 'Jan Scheurich' ; Kevin Traynor
> ; Flavio Leitner ; Aaron Conole
> ; Loftus, Ciara ; Kavanagh,
> Mark B ; Ben Pfaff
> Su
>
> On 02/08/2018 01:56 PM, Jan Scheurich wrote:
> > Hi Ilya,
> >
> > Yes, that was the consensus yesterday in the OVS-DPDK call: Revert to
> the legacy shared mempool for the 2.9 branch only prior to OVS 2.9.0
> release to avoid all issues with upgrades to 2.9 and compatibility
> complications wh
On 02/08/2018 12:19 PM, Ilya Maximets wrote:
>> Hi all,
>>
>> As discussed on the OVS-DPDK community call, I've manually reverted the per
>> port mempool changes in OVS-DPDK on a branch on my own git hub. This had to
>> be re-introduced manually due to the number of commits and work that had
>>
Hi Ilya,
> Hi,
>
> Hi, Alessandro.
>
> >
> > My name is Alessandro Rosetti, and I'm currently adding netmap support
> to
> > ovs, following an approach similar to DPDK.
>
> Good to know that someone started to work on this. IMHO, it's a good idea.
> I also wanted to try to implement this someda
While OVS userspace datapath (OVS-DPDK) supports GREv6, it does not
inter-operate with a native Linux ip6gretap tunnel. This is because
the Linux driver uses IPv6 optional headers for the Tunnel
Encapsulation Limit (RFC 2473, section 6.6).
OVS userspace simply does not parse these IPv6 extension h
7th February 2018
Attendees: Flavio, Matteo, Aaron, Ian, Sugesh, Alejandro, Jan, Billy,
Johan, Simon, Frikkie, Eelco, Kevin.
===
GENERAL
===
OVS 2.9 Release
Outstanding bug fixes
- rhel: Fix support for root user using DPDK.
-- Aaron is brewing something for this. Will give an update in
On Thu, Feb 08, 2018 at 06:14:50PM +0800, Yang, Yi wrote:
> On Thu, Feb 08, 2018 at 05:17:56AM +0800, Gregory Rose wrote:
> > On 2/7/2018 10:46 AM, Ben Pfaff wrote:
> > > On Fri, Feb 02, 2018 at 10:23:04AM -0800, Gregory Rose wrote:
> > >> On 1/31/2018 5:53 AM, Yi Yang wrote:
> > >>> v1->v2
> > >>>
The WDK 10 static analysis complains:
stt.c(427): warning C30030: Warning: Allocating executable memory via
specifying a MM_PAGE_PRIORITY type without a bitwise OR with
MdlMappingNoExecute.
Signed-off-by: Alin Gabriel Serdean
---
datapath-windows/ovsext/Stt.c | 4 ++--
1 file changed, 2 insertio
It looks a bit complicated.
What do you think about the following approach:
git diff datapath-windows/automake.mk
diff --git a/datapath-windows/automake.mk b/datapath-windows/automake.mk
index 3820041f6..164567734 100644
--- a/datapath-windows/automake.mk
+++ b/datapath-windows/automake.mk
@@ -85
Hi Alin, thanks for the review.
I personally feel we should be consistent and run configure, and have a single
make command to build both user space and kernel. What part did you find
complicated?
Thanks,
Shashank
From: aserd...@ovn.org
Sent: Thursday,
Trimming the message a bit.
-Mesaj original-
De la: ovs-dev-boun...@openvswitch.org
[mailto:ovs-dev-boun...@openvswitch.org] În numele Shashank Ram
Trimis: Thursday, February 8, 2018 7:50 PM
Către: aserd...@ovn.org; d...@openvswitch.org
Subiect: Re: [ovs-dev] [PATCH] datapath-windows: Supp
On Thu, Feb 08, 2018 at 04:40:38PM +0100, Eelco Chaudron wrote:
> While OVS userspace datapath (OVS-DPDK) supports GREv6, it does not
> inter-operate with a native Linux ip6gretap tunnel. This is because
> the Linux driver uses IPv6 optional headers for the Tunnel
> Encapsulation Limit (RFC 2473, s
From: aserd...@ovn.org
Sent: Thursday, February 8, 2018 10:43 AM
To: Shashank Ram; aserd...@ovn.org; d...@openvswitch.org
Subject: RE: [ovs-dev] [PATCH] datapath-windows: Support to selectively compile
targets
Trimming the message a bit.
-Mesaj o
Implemente un plan de prevención y corrección ante estas situaciones
Violencia en el trabajo: Protocolo anti hostigamiento sexual y laboral
15 de Febrero- Mtra. Leticia Tercero Leyzaola - 9am- 6pm
En el año 2016 la Secretaría del Trabajo y Previsión Social (STPS) presentó el
Protocolo de Actuac
On 1/24/2018 7:23 PM, Greg Rose wrote:
A previous patch added post install and post uninstall scripts which
use the weak-modules utility to make sure that openvswitch kernel
modules are copied to the correct kernel directory. While this
patch did fix some issues there are two remaining issues we
Hi Numan,
I did a test with this where I created two address sets with ~1000
addresses in them. Then I created a series of ACLs that used these two
address sets in ACLs like so:
ovn-nbctl acl-add ls0 to-lport 1000 "outport == \"lsp${COUNT}\" &&
ip4.src == \$set1 && ip4.dst == \$set2" allow
ONF extension pack 1 for OpenFlow 1.3 defines how to implement the OpenFlow
1.4 "role status" message in OpenFlow 1.3. This commit implements that
feature.
ONF-JIRA: EXT-191
Signed-off-by: Ben Pfaff
---
Documentation/topics/openflow.rst | 8 -
NEWS | 2 ++
inc
This removes the requirement of exactly two spaces before the error
description (now one or more is fine). It also makes an error message
clearer.
Signed-off-by: Ben Pfaff
---
build-aux/extract-ofp-errors | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/build-aux/extract-
Also implements the backports of relevant errors to OF1.3 as specified in
ONF extension pack 1 for OF1.3.
ONF-JIRA: EXT-237
ONF-JIRA: EXT-230
ONF-JIRA: EXT-264
Signed-off-by: Ben Pfaff
---
Documentation/topics/openflow.rst | 20 -
include/openvswitch/ofp-errors.h | 88 ++
Bundles are implemented for both OF1.3 and OF1.4+, so no need to keep it
in the list. Packet type aware pipeline is now implemented too.
Signed-off-by: Ben Pfaff
---
Documentation/topics/openflow.rst | 24
1 file changed, 24 deletions(-)
diff --git a/Documentation/topi
Greeting. I have a deal valued 9.560.650 USD. You can receive total money? Send
reply into my private email: florianda...@protonmail.ch
(mailto:florianda...@protonmail.ch)
___
dev mailing list
d...@openvswitch.org
https://mail.openvswitch.org/mailman/li
The main application scenario of this patch is that the user flow wants to
different destination addresses through different external networks.
This scenario requires a distributed route to be associated with
multiple external network logical switches.
Change l3dgw_port to l3dgw_ports in ovn_datap
The main application scenario of this patch is that the user flow wants to
different destination addresses through different external networks.
This scenario requires a distributed route to be associated with
multiple external network logical switches.
Change l3dgw_port to l3dgw_ports in ovn_datap
29 matches
Mail list logo
