On Wed, 2017-12-27 at 10:25 -0800, Ben Pfaff wrote:
> On Wed, Dec 27, 2017 at 04:22:55PM +0100, Julia Lawall wrote:
> > The email address pshe...@nicira.com listed for Pravin Shelar in
> > MAINTAINERS (OPENVSWITCH section) seems to bounce.
>
> Pravin has used a newer address recently, so I sent ou
From: wenxu
if the gro enable, ipgre receive a gre-tso package. After pop
the gre-tunnel the encapsulation and GSO_ENCAP flags should be
striped. or the packet encap again and will be dropped in
ovs_iptunnel_handle_offloads
Signed-off-by: wenxu
---
datapath/linux/compat/ip_gre.c | 2 ++
1 file
> On Dec 26, 2017, at 2:14 PM, Gregory Rose wrote:
>
> I'll continue to look into it.
I looked at this patch more carefully, and I don't see where it would cause
issues. It mostly renames a couple of things and adds a new function which
isn't used in this patch. Of course it's certainly pos
On Wed, Dec 27, 2017 at 07:48:30PM +0800, ychen wrote:
> HI, is there any policy about which fields should be wildcard when using
> megaflow match?
...
> my question is why ETH_SRC, ETH_DST is needed when using normal action?
eth_dst is needed to ensure that the packet gets forwarded to the righ
There is no sys.maxint anymore on python3. However, sys.maxsize can be
used as an integer larger than any practical list or string index.
Link: https://docs.python.org/3.1/whatsnew/3.0.html#integers
Signed-off-by: Markos Chandras
---
ovsdb/ovsdb-dot.in | 4 ++--
1 file changed, 2 insertions(+),
PEP-3110 changes the semantics for capturing exceptions in Python3
from 'except E,N' to 'except E as N'. This fixes the following problem
when building with python3
SyntaxError: invalid syntax
File "./ovsdb/ovsdb-dot.in", line 106
except ovs.db.error.Error, e:
^
The python2 print statement no longer works in python3 since the
latter uses a print function. As such, replace all instances of
'print' with 'print()'. This fixes the following build problem with
python3
> ovsdb/ovsdb-client.1.tmp
File "./ovsdb/ovsdb-dot.in", line 34
print "\t%s -> %s [%s];"
Python3 removed the iteritems() iterator and replaced it with items()
which should also work in Python2. This fixes the following build
problem on Python3:
Traceback (most recent call last):
File "./ovsdb/ovsdb-idlc.in", line 1436, in
func(*args[1:])
File "./ovsdb/ovsdb-idlc.in", line 314
Hello,
This patchset fixes some python3 issues when running the ovsdb-dot
tool with python3.
Markos Chandras (4):
ovsdb: Use items() instead of iteritems() for Python3
ovsdb: ovsdb-dot.in: Use print function for Python3
ovsdb: ovsdb-dot.in: Change exception semantics for Python3
ovsdb: ov
On Wed, Dec 27, 2017 at 04:22:55PM +0100, Julia Lawall wrote:
> The email address pshe...@nicira.com listed for Pravin Shelar in
> MAINTAINERS (OPENVSWITCH section) seems to bounce.
Pravin has used a newer address recently, so I sent out a suggested
update (for OVS):
https://patchwork.ozla
Reported-by: Julia Lawall
CC: Pravin Shelar
Signed-off-by: Ben Pfaff
---
MAINTAINERS.rst | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/MAINTAINERS.rst b/MAINTAINERS.rst
index a6deb82294e6..fec215aa40bc 100644
--- a/MAINTAINERS.rst
+++ b/MAINTAINERS.rst
@@ -66,7 +66,7 @@ Th
The email address pshe...@nicira.com listed for Pravin Shelar in
MAINTAINERS (OPENVSWITCH section) seems to bounce.
julia
___
dev mailing list
d...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-dev
OVS_NLERR prints a newline at the end of the message string, so the
message string does not need to include a newline explicitly. Done
using Coccinelle.
Signed-off-by: Julia Lawall
---
net/openvswitch/conntrack.c |4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/net/op
Drop newline at the end of a message string when the printing function adds
a newline.
The complete semantic patch that detects this issue is as shown below
(http://coccinelle.lip6.fr/). It works in two phases - the first phase
counts how many uses of a function involve a newline and how many don
Hi Ben,
On Tue, 26 Dec 2017 09:48:05 -0800
Ben Pfaff wrote:
> On Thu, Dec 21, 2017 at 10:43:06AM +0100, Jakub Sitnicki wrote:
> > If we cannot talk to ovs-vswitchd process for some reason, e.g. it has
> > terminated prematurely, we want to fail the test as soon as possible.
> >
> > Otherwise th
HI, is there any policy about which fields should be wildcard when using
megaflow match?
exp 1:
table=0, priorIty=0,actions=NORMAL
then the datapath flow is like that:
recirc_id(0),in_port(3),eth(src=b6:49:dd:5d:3a:a6,dst=2e:b5:7b:d6:52:c2),eth_type(0x0806),
packets:0, bytes:0, used:never, ac
___
dev mailing list
d...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-dev
Hi Dear,
Reading your profile has given me courage in search of a reasponsable
and trust worthy Fellow. The past has treated me so awfully but now I
am ready to move on despite of my health condition. I will like to
have a sincere and important discussion with you that will be in your
favor likewi
18 matches
Mail list logo