Since python version 3.7 (and some 3.6+ versions) regexp engine
changed to treat the wrong escape sequences as errors. Previously,
if the replace string had something like '\u', '\u' was
qualified as a bad escape sequence and treated just as a sequence
of characters '\' and 'u'. But know this
___
dev mailing list
d...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-dev
> On 14/01/2019 13:33, Ilya Maximets wrote:
> > On 14.01.2019 15:51, Ian Stokes wrote:
> >> On 1/11/2019 7:37 PM, Ian Stokes wrote:
> >>> On 1/11/2019 4:14 PM, Ilya Maximets wrote:
> Nothing significantly changed since the previous versions.
> This patch set effectively breaks following
On 01/15/2019 10:44 AM, Nitin Katiyar wrote:
>
>
>> -Original Message-
>> From: Ian Stokes [mailto:ian.sto...@intel.com]
>> Sent: Tuesday, January 15, 2019 5:06 AM
>> To: Nitin Katiyar ; ovs-dev@openvswitch.org;
>> Kevin Traynor ; Ilya Maximets
>>
>> Subject: Re: [ovs-dev] [PATCH v5]
> Dpdk port representors were introduced in dpdk versions 18.xx.
> Prior to port representors there was a one-to-one relationship between an
> rte device (e.g. PCI bus) and an eth device (referenced as dpdk port id in
> OVS). With port representors the relationship becomes one-to-many rte
>
On 01/15/2019 09:47 AM, Ophir Munk wrote:
> Dpdk port representors were introduced in dpdk versions 18.xx.
> Prior to port representors there was a one-to-one relationship
> between an rte device (e.g. PCI bus) and an eth device (referenced as
> dpdk port id in OVS). With port representors the
Hmm. I received 5 copies of this patch.
Are they different or you just have some strange issues with sending mails?
Best regards, Ilya Maximets.
On 15.01.2019 12:47, Ophir Munk wrote:
> Dpdk port representors were introduced in dpdk versions 18.xx.
> Prior to port representors there was a
My apologies.
My outlook server has issues.
All patches are the same.
Regards,
Ophir
> -Original Message-
> From: Ilya Maximets
> Sent: Tuesday, January 15, 2019 12:09 PM
> To: Ophir Munk ; ovs-dev@openvswitch.org
> Cc: Ian Stokes ; Olga Shern ;
> Kevin Traynor
> Subject: Re: [PATCH
> -Original Message-
> From: Federico Iezzi [mailto:fie...@redhat.com]
> Sent: Monday, January 14, 2019 8:54 PM
> To: Nitin Katiyar
> Cc: ovs-dev@openvswitch.org
> Subject: Re: [ovs-dev] [PATCH v5] Adding support for PMD auto load
> balancing
>
> Maybe it's a bit late for this series,
> -Original Message-
> From: Ian Stokes [mailto:ian.sto...@intel.com]
> Sent: Tuesday, January 15, 2019 5:06 AM
> To: Nitin Katiyar ; ovs-dev@openvswitch.org;
> Kevin Traynor ; Ilya Maximets
>
> Subject: Re: [ovs-dev] [PATCH v5] Adding support for PMD auto load
> balancing
>
> On
Bleep bloop. Greetings wangyunjian, I am a robot and I have tried out your
patch.
Thanks for your contribution.
I encountered some error that I wasn't expecting. See the details below.
git-am:
fatal: corrupt patch at line 7
Repository lacks necessary blobs to fall back on 3-way merge.
Cannot
Bleep bloop. Greetings David Marchand, I am a robot and I have tried out your
patch.
Thanks for your contribution.
I encountered some error that I wasn't expecting. See the details below.
checkpatch:
WARNING: Unexpected sign-offs from developers who are not authors or co-authors
or
Hi, Ben.
This is not a directly unicode related bug. It's a change
in python regex library.
I've sent a fix there:
https://patchwork.ozlabs.org/patch/1025212/
Please, check it on your system.
Best regards, Ilya Maximets.
___
dev mailing list
On Mon, Jan 14, 2019 at 12:12:34PM +, wangyunjian wrote:
> Hi,
>
> I found a problem the userspace datapath failed to create a
> new datapath flow for the QinQ packet. When getting mask from
> nlattrs with the mask include ip,udp,etc, it parsed 802.1Q
> header wrongly.
>
> This patch fixes
On Mon, Jan 14, 2019 at 08:15:36AM -0600, Terry Wilson wrote:
> This fix was reverted because it depended on a small bit of code
> in a patch that was reverted that changed some python/ovs testing
> and build. The fix is still necessary.
>
> The OVS C-based JSON parser operates on bytes, so the
On Mon, Jan 14, 2019 at 04:20:30PM +0100, Timothy Redaelli wrote:
> Fixes: be51cd417343 ("ovs-actions: New document describing OVS actions in
> detail.")
> Signed-off-by: Timothy Redaelli
Thanks! I applied these to master.
___
dev mailing list
On 12/12/2018 22:18, Ian Stokes wrote:
> From: Sugesh Chandran
>
> Currently devices that do not support configuring flow control via the eth_dev
> API (e.g. SRIOV VFs) will fail during configuration setup when the interface
> is added even if flow control is not requested. This is due to
>
Thanks, applied to master.
On Thu, Dec 13, 2018 at 10:18:20AM -0600, Terry Wilson wrote:
> Signed-off-by: Terry Wilson
> ---
> Documentation/ref/ovsdb.7.rst | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentation/ref/ovsdb.7.rst b/Documentation/ref/ovsdb.7.rst
>
On Mon, Jan 14, 2019 at 06:04:32PM +0300, Ilya Maximets wrote:
> Current checkpatch rules matches only OVS 'FOR_EACH' loops.
> This change will apply same style checks for DPDK iterators
> like 'RTE_ETH_FOREACH_MATCHING_DEV () {}'.
>
> Signed-off-by: Ilya Maximets
Thanks, applied to master.
On Tue, Jan 15, 2019 at 05:43:48PM +0300, Ilya Maximets wrote:
> Hi, Ben.
> This is not a directly unicode related bug. It's a change
> in python regex library.
>
> I've sent a fix there:
> https://patchwork.ozlabs.org/patch/1025212/
>
> Please, check it on your system.
Thanks!
On Tue, Jan 15, 2019 at 5:42 AM Han Zhou wrote:
> Hi Numan,
>
> The feature looks very good overall. I have some more comments inlined.
>
Thank Han for the review and the comments.
You are right. The logical port's mac flaps too. I had to read the commit
message again to
recall :)
> On Thu,
On Tue, Jan 15, 2019 at 05:03:00PM +0300, Ilya Maximets wrote:
> Since python version 3.7 (and some 3.6+ versions) regexp engine
> changed to treat the wrong escape sequences as errors. Previously,
> if the replace string had something like '\u', '\u' was
> qualified as a bad escape sequence
On Mon, Jan 14, 2019 at 2:35 PM Terry Wilson wrote:
>
> This fix was reverted because it depended on a small bit of code
> in a patch that was reverted that changed some python/ovs testing
> and build. The fix is still necessary.
>
> The OVS C-based JSON parser operates on bytes, so the
From: Numan Siddique
In the case of OpenStack + OVN, when the VMs are booted on
hypervisors supporting SR-IOV nics, there are no OVS ports
for these VMs. When these VMs sends DHCPv4, DHPCv6 or IPv6
Router Solicitation requests, the local ovn-controller
cannot reply to these packets. OpenStack
From: Numan Siddique
Up until now, OVN rpms were generated as sub packages of OpenvSwitch.
This patch now splits it and makes OVN rpms independent.
A new spec file - ovn-fedora.spec.in is added for this.
The openvswitch-fedora.spec.in has been modified to create only
OpenvSwitch packages.
One of the more common cases of allocation size calculations is finding the
size of a structure that has a zero-sized array at the end, along with memory
for some number of elements for that array. For example:
struct foo {
int stuff;
struct boo entry[];
};
instance =
> On 01/15/2019 09:47 AM, Ophir Munk wrote:
> > Dpdk port representors were introduced in dpdk versions 18.xx.
> > Prior to port representors there was a one-to-one relationship between
> > an rte device (e.g. PCI bus) and an eth device (referenced as dpdk
> > port id in OVS). With port
>From fc0a9e1329573692c04438370f85e87125a268b0 Mon Sep 17 00:00:00 2001
From: Prashanth Iyengar
Date: Mon, 14 Jan 2019 12:53:11 -0800
Subject: [PATCH] Fix OpenFlow v1.3.4 Conf test failures: 430.500, 430.510
This commit adds additional verification to nx_pull_header__() in
lib/nx-match.c to
$1,000,000.00 dollars has been donated to you by Maureen David Kaltschmidt who
won the Powerball Jackpot of $758.7 million Dollars. Contact her via Email:
maureendavidkaltschm...@gmail.com for more details
___
dev mailing list
d...@openvswitch.org
On Fri, Jan 11, 2019 at 10:09:05AM -0800, Justin Pettit wrote:
>
> > On Aug 30, 2018, at 1:00 PM, Ben Pfaff wrote:
> >
> > Signed-off-by: Ben Pfaff
> > ---
> > ofproto/ofproto.c | 84
> > +--
> > 1 file changed, 44 insertions(+), 40
Some small fixes to make the ftp alg behave a little better.
I tried to come up with better tests but I am not too sure if we want to
have a dependency on yet another external tool for it (lftp).
Changelog since v3:
- applied Darrell comments
- more child connections, little style change in
Thanks for the review. I fixed the obvious stuff and just dropped the
request.
On Fri, Jan 11, 2019 at 01:07:36AM -0800, Justin Pettit wrote:
>
> > On Aug 30, 2018, at 1:00 PM, Ben Pfaff wrote:
> > @@ -418,8 +425,11 @@ ofputil_decode_table_features(struct ofpbuf *msg,
> >
> > struct
Greetings From Mrs Awen Ken.
I wrote you two days ago expecting that you would reply as regards the urgent
information I passed to you. Anyway, I don't know if you did receive it or not
that is the reason I am sending this reminder.
I write to solicit for your partnership for a desired project
Port rx queues that have not been statically assigned to PMDs are currently
assigned based on periodically sampled load measurements.
The assignment is performed at specific instances – port addition, port
deletion, upon reassignment request via CLI etc.
Due to change in traffic pattern over time
From: Yunjian Wang
A problem the userspace datapath failed to create a new datapath flow
when dealing with QinQ packets(the flow includeing ip,udp,etc). L2-L5
header should be considered before parsing the second 802.1Q header.
Fixes: f0fb825a3785 ("Add support for 802.1ad (QinQ tunneling)")
Hi Ilya,
Please find comments inline
> -Original Message-
> From: Ilya Maximets
> Sent: Monday, January 14, 2019 12:11 PM
> To: Ophir Munk ; ovs-dev@openvswitch.org
> Cc: Asaf Penso ; Ian Stokes ;
> Shahaf Shuler ; Thomas Monjalon
> ; Olga Shern ; Kevin
> Traynor
> Subject: Re: [PATCH
Some small fixes to make the ftp alg behave a little better.
I tried to come up with better tests but I am not too sure if we want to
have a dependency on yet another external tool for it (lftp).
Changelog since v3:
- applied Darrell comments
- more child connections, little style change in
The ftp alg deals with packets in two ways for the command connection:
either they are inspected and can be mangled when nat is enabled
(CT_FTP_CTL_INTEREST) or they just go through without being modified
(CT_FTP_CTL_OTHER).
For CT_FTP_CTL_INTEREST packets, we must both adjust the packet tcp seq
On Tue, Jan 15, 2019 at 8:20 AM Darrell Ball wrote:
>
> On 1/14/19, 4:49 AM, "ovs-dev-boun...@openvswitch.org on behalf of David
> Marchand" david.march...@redhat.com> wrote:
>
> On Mon, Jan 14, 2019 at 7:32 AM Darrell Ball wrote:
>
> > 4/ I added another test below for reverse skew.
From: Yunjian Wang
A problem the userspace datapath failed to create a new datapath flow
when dealing with QinQ packets(the flow includeing ip,udp,etc). L2-L5
header should be considered before parsing the second 802.1Q header.
Fixes: f0fb825a3785 ("Add support for 802.1ad (QinQ tunneling)")
On 15.01.2019 11:39, Ophir Munk wrote:
> Hi Ilya,
> Please find comments inline
>
>> -Original Message-
>> From: Ilya Maximets
>> Sent: Monday, January 14, 2019 12:11 PM
>> To: Ophir Munk ; ovs-dev@openvswitch.org
>> Cc: Asaf Penso ; Ian Stokes ;
>> Shahaf Shuler ; Thomas Monjalon
>> ;
Dpdk port representors were introduced in dpdk versions 18.xx.
Prior to port representors there was a one-to-one relationship
between an rte device (e.g. PCI bus) and an eth device (referenced as
dpdk port id in OVS). With port representors the relationship becomes
one-to-many rte device to eth
We offer loans with instant approval online at 3% interest. Multi-Purpose
Loans Available. We offer our Loans to our clients In ($)USD,(£)GBP,(€)Euro
in the following categories. Personal Loan,Student Loans, Real Estate Loan,
Business Loan and others. Contact us Via email
Dpdk port representors were introduced in dpdk versions 18.xx.
Prior to port representors there was a one-to-one relationship
between an rte device (e.g. PCI bus) and an eth device (referenced as
dpdk port id in OVS). With port representors the relationship becomes
one-to-many rte device to eth
Dpdk port representors were introduced in dpdk versions 18.xx.
Prior to port representors there was a one-to-one relationship
between an rte device (e.g. PCI bus) and an eth device (referenced as
dpdk port id in OVS). With port representors the relationship becomes
one-to-many rte device to eth
Dpdk port representors were introduced in dpdk versions 18.xx.
Prior to port representors there was a one-to-one relationship
between an rte device (e.g. PCI bus) and an eth device (referenced as
dpdk port id in OVS). With port representors the relationship becomes
one-to-many rte device to eth
46 matches
Mail list logo
