Re: [ovs-discuss] HW virt functions support

2012-01-31 Thread Jesse Gross
On Tue, Jan 31, 2012 at 3:42 PM, potworyk wrote: > 2012/2/1 Jesse Gross : >> On Tue, Jan 31, 2012 at 3:13 PM, potworyk wrote: >>> 2012/1/31 Jesse Gross : On Tue, Jan 31, 2012 at 2:27 PM, potworyk wrote: > Hi, > > I've searched for information about hardware support in Open vSwit

Re: [ovs-discuss] HW virt functions support

2012-01-31 Thread potworyk
2012/2/1 Jesse Gross : > On Tue, Jan 31, 2012 at 3:13 PM, potworyk wrote: >> 2012/1/31 Jesse Gross : >>> On Tue, Jan 31, 2012 at 2:27 PM, potworyk wrote: Hi, I've searched for information about hardware support in Open vSwitch but there is no clear statment. Does Open vSwitch

Re: [ovs-discuss] HW virt functions support

2012-01-31 Thread Jesse Gross
On Tue, Jan 31, 2012 at 3:13 PM, potworyk wrote: > 2012/1/31 Jesse Gross : >> On Tue, Jan 31, 2012 at 2:27 PM, potworyk wrote: >>> Hi, >>> >>> I've searched for information about hardware support in Open vSwitch >>> but there is no clear statment. Does Open vSwitch use SR-IOV, Intel >>> VMDq or o

Re: [ovs-discuss] HW virt functions support

2012-01-31 Thread potworyk
2012/1/31 Jesse Gross : > On Tue, Jan 31, 2012 at 2:27 PM, potworyk wrote: >> Hi, >> >> I've searched for information about hardware support in Open vSwitch >> but there is no clear statment. Does Open vSwitch use SR-IOV, Intel >> VMDq or other? Where I can find some information about it? > > Thos

Re: [ovs-discuss] HW virt functions support

2012-01-31 Thread Jesse Gross
On Tue, Jan 31, 2012 at 2:27 PM, potworyk wrote: > Hi, > > I've searched for information about hardware support in Open vSwitch > but there is no clear statment. Does Open vSwitch use SR-IOV, Intel > VMDq or other? Where I can find some information about it? Those types of hardware offloads don't

[ovs-discuss] HW virt functions support

2012-01-31 Thread potworyk
Hi, I've searched for information about hardware support in Open vSwitch but there is no clear statment. Does Open vSwitch use SR-IOV, Intel VMDq or other? Where I can find some information about it? ___ discuss mailing list discuss@openvswitch.org http:

Re: [ovs-discuss] ovs-brcompatd on CentOS/RHEL 6.x

2012-01-31 Thread Ben Pfaff
On Tue, Jan 31, 2012 at 10:21:46AM +0100, Frido Roose wrote: > I'm currently trying openvswitch in a KVM environment on CentOS 6.2, and > I'm having a problem with the compatibility mode when running ovs-brcompatd. > > # ovs-vsctl add-br vbr314 > # brctl show > bridge name bridge id STP enabled in

Re: [ovs-discuss] check overlap flag for add-flow command in openvswitch

2012-01-31 Thread Ben Pfaff
On Tue, Jan 31, 2012 at 09:59:48PM +0530, selen jia wrote: > if i edit this code ofp-parse.c and* add fm->flags=2* then i do get the > overlap error if i add same flow again but i want to know how to enable it > without editing code. > > > there must be somne commandto request check for overlap

Re: [ovs-discuss] IP address wildcard mask do not follow openflow 1.0 spec

2012-01-31 Thread Iben Rodriguez
Hi Edward, I think I found the culprit here... Correct me if I'm wrong but you're reading this doc... right? This spec for openflow defines how tools like openvswitch should work "under the hood". It doesn't say that that's how we as consumers of the tool should interact with it. What if they d

[ovs-discuss] check overlap flag for add-flow command in openvswitch

2012-01-31 Thread selen jia
Helo all, Im using openvswitch 1.2.2 and i am doing following i add a flow and then try to add same flow again, now openflow 1.0 spec says i should get *Overlap erro*r but i dont get it. In source code i saw in openflow.h enum ofp_flow_mod_flags { *OFPFF_SEND_FLOW_REM = 1 << 0, /* Send flow

Re: [ovs-discuss] IP address wildcard mask do not follow openflow 1.0 spec

2012-01-31 Thread Rob Sherwood
Fwiw, I would argue that the ovs-ofctl does the right thing which is "make it easier for a human" and the OF spec (arguably?) does the right thing of "make it easier for a machine". The original poster seems to be making an assumption that these two encoding should be the same, and I'm with Justin

Re: [ovs-discuss] ovs-brcompatd on CentOS/RHEL 6.x

2012-01-31 Thread Frido Roose
Well, actually this is exactly the same problem as: http://openvswitch.org/pipermail/discuss/2011-September/005768.html No answers in that thread, so I was wondering if there was any progress on this topic. Br, Frido On Tue, Jan 31, 2012 at 10:40 AM, Frido Roose wrote: > Yep, > > # lsmod | gre

Re: [ovs-discuss] ovs-brcompatd on CentOS/RHEL 6.x

2012-01-31 Thread Frido Roose
Yep, # lsmod | grep openvswitch openvswitch_mod82997 2 brcompat_mod # lsmod | egrep "openvswitch_mod|brcompat_mod" brcompat_mod5713 0 openvswitch_mod82997 2 brcompat_mod # grep COMPAT /etc/sysconfig/openvswitch BRCOMPAT=yes # ps auxw | grep brcompat root 23731

Re: [ovs-discuss] ovs-brcompatd on CentOS/RHEL 6.x

2012-01-31 Thread Justin Pettit
I assume you have the kernel module "brcompat_mod.ko" loaded? --Justin On Jan 31, 2012, at 1:21 AM, Frido Roose wrote: > Hello, > > I'm currently trying openvswitch in a KVM environment on CentOS 6.2, and I'm > having a problem with the compatibility mode when running ovs-brcompatd. > > # ov

[ovs-discuss] ovs-brcompatd on CentOS/RHEL 6.x

2012-01-31 Thread Frido Roose
Hello, I'm currently trying openvswitch in a KVM environment on CentOS 6.2, and I'm having a problem with the compatibility mode when running ovs-brcompatd. # ovs-vsctl add-br vbr314 # brctl show bridge name bridge id STP enabled interfaces vbr314 /sys/class/net/vbr314/bridge: No such file or dir

Re: [ovs-discuss] IP address wildcard mask do not follow openflow 1.0 spec

2012-01-31 Thread Justin Pettit
I've seen nothing that indicates there's a problem. I'm sorry you're confused about the difference between what's on the wire and what's being displayed to the user. I don't know how else to convince you that it's working properly, so I'm going to stop. --Justin On Jan 31, 2012, at 1:00 AM,

Re: [ovs-discuss] IP address wildcard mask do not follow openflow 1.0 spec

2012-01-31 Thread edward wilson
hi, if use the metric /24 then ovs-ofctl dump-flows shows me nw_src=10.2.3.*, that means internally also it is treated as cidr mask, because as per openflow spec dump-flows output should be nw_src=10.*.*.* On Tue, Jan 31, 2012 at 1:27 PM, Justin Pettit wrote: > If you're concerned/confused abo