Re: [ovs-dev] [GIT net] Open vSwitch

From: Jesse Gross Date: Wed, 6 Feb 2013 19:14:55 -0800 > One bug fix for net/3.8 for a long standing problem that was reported a few > times recently. > > The following changes since commit a49f0d1ea3ec94fc7cf33a7c36a16343b74bd565: > > Linux 3.8-rc1 (2012-12-21 17:19:00 -0800) > > are avail

Re: [ovs-dev] Does ovs-vsctl add-br br01 really create a bridge just like brctl add-br br01?

Hi Thanks your reply. Yes, I read that manual several times before i sent the previous post here. This manual tell me that ovs-vsctl is a db client to configure Open vSwitch configuration database maintained by ovsdb-server. So when you execute ovs-vsctl add-br br01 command, it actually only s

[ovs-dev] [PATCH 2/2] tunnel: Treat in_key=0 the same as a missing in_key.

The documented behavior of ovs is that a missing key is the same as a zero key. However, the tunneling code actually treated them differently. This could cause problems with tunneling modes such as vxlan which always have a key. Specifically, a tunnel with no key configured, would send have to s

[ovs-dev] [PATCH 1/2] tunnel: Log tunneling changes at INFO level.

These log messages occur infrequently, and are quite useful when debugging problems after the fact. So they should be logged at info level which makes them more readily available. Signed-off-by: Ethan Jackson --- ofproto/tunnel.c |4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) dif

Re: [ovs-dev] [PATCH] classifier: Skip tables if priorities guarantee no match.

On Thu, Feb 07, 2013 at 10:04:14PM +, Rajahalme, Jarno (NSN - FI/Espoo) wrote: > > On Feb 7, 2013, at 22:36 , ext Ben Pfaff wrote: > > > With complicated flow tables and multiple levels of resubmit, I see > > flow setup performance improvements of up to 5-6% with this patch. > > > > I play

[ovs-dev] [PATCH] stream-unix: append ovs_rundir to socket

If socket path specified is relative to ovs_rundir(), append the directory name to in unix_open and punix_open. Freed the new newly allocated strings. Also included the change in bridge.c to relax the whitelist check, only if there is no /. Signed-off-by: Pavithra Ramesh --- lib/stream-unix.c |

[ovs-dev] [PATCH 2/2] classifier: Maintain tables in descending priority order.

Signed-off-by: Jarno Rajahalme --- lib/classifier.c | 109 ++ lib/classifier.h |2 + lib/list.h |8 3 files changed, 88 insertions(+), 31 deletions(-) diff --git a/lib/classifier.c b/lib/classifier.c index 2ed0013..f3df676

[ovs-dev] [PATCH 1/2] Optimize classifier by maintaining the priority of the highest priority rule in each table.

Signed-off-by: Jarno Rajahalme --- lib/classifier.c| 57 --- lib/classifier.h|2 ++ tests/test-classifier.c | 13 +++ 3 files changed, 64 insertions(+), 8 deletions(-) diff --git a/lib/classifier.c b/lib/classifier.c in

Re: [ovs-dev] [PATCH] classifier: Skip tables if priorities guarantee no match.

On Feb 7, 2013, at 22:36 , ext Ben Pfaff wrote: > With complicated flow tables and multiple levels of resubmit, I see > flow setup performance improvements of up to 5-6% with this patch. > I played around with the same issue last week and came up with a little bit different solution. I think I

[ovs-dev] [PATCH] classifier: Skip tables if priorities guarantee no match.

With complicated flow tables and multiple levels of resubmit, I see flow setup performance improvements of up to 5-6% with this patch. Signed-off-by: Ben Pfaff --- lib/classifier.c | 30 ++ lib/classifier.h | 16 +++- 2 files changed, 41 insertions(+),

[ovs-dev] [PATCH] stream-unix: append ovs_rundir to socket

Incorporated Ben's comments. If socket path specified is relative to ovs_rundir(), append the directory name to in unix_open and punix_open. Also included the change in bridge.c to relax the whitelist check, only if there is no /. Signed-off-by: Pavithra Ramesh --- lib/stream-unix.c | 20 +++

[ovs-dev] [PATCH] ofproto-dpif: Reduce number of get_ofp_port() calls during flow xlate.

Until now the flow translation code has done one get_ofp_port() call initially to check for special processing, then one for each level of action processing. Only one call is actually necessary, though, because the in_port of a flow doesn't change in ordinary circumstances, and so this commit elim

Re: [ovs-dev] [PATCH] stream-unix: append ovs_rundir to socket If socket path specified is relative to ovs_rundir(), append the directory name to in unix_open.

On Wed, Feb 06, 2013 at 11:28:55AM -0800, Pavithra Ramesh wrote: > Taken care of the memroy leak, used xasprintf instead. > Also included the change in bridge.c to relax the whitelist > check. > > Signed-off-by: Pavithra Ramesh > --- > lib/stream-unix.c | 11 ++- > vswitchd/bridge.c |

Re: [ovs-dev] Does ovs-vsctl add-br br01 really create a bridge just like brctl add-br br01?

On Thu, Feb 07, 2013 at 08:40:48PM +0800, ?? wrote: > Recently, i am reading source code of ovs-vsctl. i get confused. what > confused me is ovs-vsctl doesn't send instruction to kernel module, seems > that it only store br information into br table. As we know, brctl add-br > will send in

[ovs-dev] GLUCKWUNSCHE [ IHRE E-mail HAT GEWONNEN {REF NR, 575061725 } ] !!(Warning: Endgültige Anmeldung)

UNITED STATES OF AMERICA LOTTO INC. ADRESSE: OSTWESTLANDSTRASSE 1325 STADT: SILBERNER FRUHLING STATE/PROVINCE: MARYLAND POSTCODE: 20110 LAND: USA INC. REF NR: .364758679 STAPEL NR: .6485769789/646 ***

[ovs-dev] Does ovs-vsctl add-br br01 really create a bridge just like brctl add-br br01?

Hi Recently, i am reading source code of ovs-vsctl. i get confused. what confused me is ovs-vsctl doesn't send instruction to kernel module, seems that it only store br information into br table. As we know, brctl add-br will send instruction to kernel module by ioctl with flag SIOCSIFBR, and