Re: [ovs-discuss] ingress_policing_rate rule taking too long to kick in

2016-09-11 Thread Frederico
Interesting. Initially I had no ingress policy set up and after a huge amount of traffic I set it to 1024 (along with the burst at 80%) and observed a delay. Then I started my experiment adding a broad policy (4096 and 80% burst) before triggering the syn flood. This time when the new incoming pol

Re: [ovs-discuss] ingress_policing_rate rule taking too long to kick in

2016-09-11 Thread Ben Pfaff
OVS just configures the kernel QoS implementation. If there's a delay, it comes from the kernel and OVS has no influence over it. On Sun, Sep 11, 2016 at 03:16:25PM -0300, Frederico wrote: > No luck. I have tried different burst amounts. Ranging from 0 to 1024 > and in every attempt it still take

Re: [ovs-discuss] ingress_policing_rate rule taking too long to kick in

2016-09-11 Thread Frederico
Ben, No luck. I have tried different burst amounts. Ranging from 0 to 1024 and in every attempt it still takes some 5 to 10 seconds until I see any effect. Also, the documentation doesn't say anything about any delay regarding ingress policies. 2016-09-11 1:01 GMT-03:00 Ben Pfaff : > On Sat, Sep

Re: [ovs-discuss] Datapath is not compiled

2016-09-11 Thread Ben Pfaff
On Sun, Sep 11, 2016 at 12:59:32AM -0700, Justin Pettit wrote: > > > On Sep 10, 2016, at 10:48 PM, Nomad Esst wrote: > > > > Hi > > > > I'm trying to compile OVS from source in FreeBSD 10.3 AMD64 but it seems > > that datapath is not compiled when I try to compile the source code. I have > >

Re: [ovs-discuss] Datapath is not compiled

2016-09-11 Thread Justin Pettit
> On Sep 10, 2016, at 10:48 PM, Nomad Esst wrote: > > Hi > > I'm trying to compile OVS from source in FreeBSD 10.3 AMD64 but it seems that > datapath is not compiled when I try to compile the source code. I have made > some modifications in datapath source code but these sources are not compi