RE: Timing issue with Dummynet on high kernel timer interrupt

2015-11-06 Thread Ian Smith
On Sat, 7 Nov 2015 01:51:29 +, Rasool Al-Saadi wrote: > On Saturday, 7 November 2015 2:05 AM, Hans Petter Selasky wrote: > > On 11/06/15 11:08, Luigi Rizzo wrote: > > > On Fri, Nov 6, 2015 at 10:52 AM, Hans Petter Selasky > > wrote: > > >> On 11/06/15 09:50, Luigi Rizzo wrote: > > >>>

RE: Timing issue with Dummynet on high kernel timer interrupt

2015-11-06 Thread Bruce Evans
On Sat, 7 Nov 2015, Rasool Al-Saadi wrote: On Saturday, 7 November 2015 2:05 AM, Hans Petter Selasky wrote: ... It might be worth trying to set: kern.eventtimer.periodic=1 In /boot/loader.conf . Can you test that too? You need to reboot before the setting takes into effect. You don't need

RE: Timing issue with Dummynet on high kernel timer interrupt

2015-11-06 Thread Rasool Al-Saadi
On Saturday, 7 November 2015 2:05 AM, Hans Petter Selasky wrote: > On 11/06/15 11:08, Luigi Rizzo wrote: > > On Fri, Nov 6, 2015 at 10:52 AM, Hans Petter Selasky > wrote: > >> On 11/06/15 09:50, Luigi Rizzo wrote: > >>> > >>> On Fri, Nov 6, 2015 at 9:44 AM, Hans Petter Selasky > >>> > >>> wrot

Re: Timing issue with Dummynet on high kernel timer interrupt

2015-11-06 Thread Adrian Chadd
On 6 November 2015 at 12:58, Ian Lepore wrote: > On Fri, 2015-11-06 at 11:15 -0800, Adrian Chadd wrote: >> Ideally there'd be both behaviours: >> >> * You'd specify whether a timer/sleep needs to be exact or can >> withstand some jitter (which is what linux provides); and >> * You can communicate

Re: Timing issue with Dummynet on high kernel timer interrupt

2015-11-06 Thread Ian Lepore
On Fri, 2015-11-06 at 11:15 -0800, Adrian Chadd wrote: > Ideally there'd be both behaviours: > > * You'd specify whether a timer/sleep needs to be exact or can > withstand some jitter (which is what linux provides); and > * You can communicate to the kernel its aggressiveness for coalescing > wake

Re: Timing issue with Dummynet on high kernel timer interrupt

2015-11-06 Thread John-Mark Gurney
Adrian Chadd wrote this message on Fri, Nov 06, 2015 at 11:15 -0800: > Ideally there'd be both behaviours: > > * You'd specify whether a timer/sleep needs to be exact or can > withstand some jitter (which is what linux provides); and Isn't that what the precision argument in callout is for? See

Re: netstat -B "Recv"

2015-11-06 Thread Christian Peron
It needs to get fixed.. let me generate a patch for you and you can test it. > On Nov 5, 2015, at 8:51 AM, el...@sentor.se wrote: > > On Thu, 5 Nov 2015, Alexander V. Chernikov wrote: > >> >> >> 04.11.2015, 19:55, "el...@sentor.se" : >>> Hi! >>> >>> Question: >>> What do the Recv column in '

Re: Timing issue with Dummynet on high kernel timer interrupt

2015-11-06 Thread Adrian Chadd
Ideally there'd be both behaviours: * You'd specify whether a timer/sleep needs to be exact or can withstand some jitter (which is what linux provides); and * You can communicate to the kernel its aggressiveness for coalescing wakeups. Teaching powerd to flip on/off a sysctl for this isn't that t

Re: Timing issue with Dummynet on high kernel timer interrupt

2015-11-06 Thread Bruce Evans
On Fri, 6 Nov 2015, Ian Lepore wrote: On Fri, 2015-11-06 at 17:51 +0100, Hans Petter Selasky wrote: On 11/06/15 17:43, Ian Lepore wrote: On Fri, 2015-11-06 at 17:28 +0100, Hans Petter Selasky wrote: Hi, Do the test II results change with this setting? sysctl kern.timecounter.allowedde

Re: Timing issue with Dummynet on high kernel timer interrupt

2015-11-06 Thread Ian Lepore
On Fri, 2015-11-06 at 17:57 +0100, Hans Petter Selasky wrote: > On 11/06/15 17:51, Hans Petter Selasky wrote: > > On 11/06/15 17:43, Ian Lepore wrote: > > > On Fri, 2015-11-06 at 17:28 +0100, Hans Petter Selasky wrote: > > > > Hi, > > > > > > > > Do the test II results change with this setting? >

Re: Timing issue with Dummynet on high kernel timer interrupt

2015-11-06 Thread Ian Lepore
On Fri, 2015-11-06 at 17:51 +0100, Hans Petter Selasky wrote: > On 11/06/15 17:43, Ian Lepore wrote: > > On Fri, 2015-11-06 at 17:28 +0100, Hans Petter Selasky wrote: > > > Hi, > > > > > Do the test II results change with this setting? > > > >sysctl kern.timecounter.alloweddeviation=0 > > >

Re: Timing issue with Dummynet on high kernel timer interrupt

2015-11-06 Thread Hans Petter Selasky
On 11/06/15 17:51, Hans Petter Selasky wrote: On 11/06/15 17:43, Ian Lepore wrote: On Fri, 2015-11-06 at 17:28 +0100, Hans Petter Selasky wrote: Hi, Do the test II results change with this setting? sysctl kern.timecounter.alloweddeviation=0 Yes, it looks much better: debug.total: 10

Re: Timing issue with Dummynet on high kernel timer interrupt

2015-11-06 Thread Hans Petter Selasky
On 11/06/15 17:43, Ian Lepore wrote: On Fri, 2015-11-06 at 17:28 +0100, Hans Petter Selasky wrote: Hi, Do the test II results change with this setting? sysctl kern.timecounter.alloweddeviation=0 Yes, it looks much better: debug.total: 10013 -> 0 debug.total: 10013 -> 0 debug.total: 1

Re: Timing issue with Dummynet on high kernel timer interrupt

2015-11-06 Thread Ian Lepore
On Fri, 2015-11-06 at 17:28 +0100, Hans Petter Selasky wrote: > Hi, > > I spent some time to write a test application to investigate this > issue > and I found some irregularities, that when > kern.eventtimer.periodic=0, > the timer appears to run very irregular. > > Test software: > ==

Re: Timing issue with Dummynet on high kernel timer interrupt

2015-11-06 Thread Hans Petter Selasky
Hi, I spent some time to write a test application to investigate this issue and I found some irregularities, that when kern.eventtimer.periodic=0, the timer appears to run very irregular. Test software: == fetch http://home.selasky.org:8192/privat/callout_test_dummynet.tar.gz tar

[Bug 156226] [lagg]: failover does not announce the failover to switch

2015-11-06 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=156226 Steven Hartland changed: What|Removed |Added Assignee|freebsd-net@FreeBSD.org |s...@freebsd.org -- You are rec

Re: Timing issue with Dummynet on high kernel timer interrupt

2015-11-06 Thread Hans Petter Selasky
On 11/06/15 11:08, Luigi Rizzo wrote: On Fri, Nov 6, 2015 at 10:52 AM, Hans Petter Selasky wrote: On 11/06/15 09:50, Luigi Rizzo wrote: On Fri, Nov 6, 2015 at 9:44 AM, Hans Petter Selasky wrote: ... Hi, The C_DIRECT_EXEC flag reduces task switching overhead, that you don't have to wakeup

Re: tap(4) and host-only networking between host and guest

2015-11-06 Thread Willem Jan Withagen
On 6-11-2015 09:09, Eugene Grosbein wrote: > On 06.11.2015 07:59, Craig Rodrigues wrote: >> On Thu, Nov 5, 2015 at 4:36 PM, Miroslav Lachman <000.f...@quip.cz> wrote: >> >>> Eugene Grosbein wrote on 11/05/2015 18:06: >>> Yes, it is. And there is a solution: https://bugs.freebsd.org/bugzil

[Bug 156226] [lagg]: failover does not announce the failover to switch

2015-11-06 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=156226 Kubilay Kocak changed: What|Removed |Added Keywords||needs-patch CC|

Re: Timing issue with Dummynet on high kernel timer interrupt

2015-11-06 Thread Luigi Rizzo
On Fri, Nov 6, 2015 at 10:52 AM, Hans Petter Selasky wrote: > On 11/06/15 09:50, Luigi Rizzo wrote: >> >> On Fri, Nov 6, 2015 at 9:44 AM, Hans Petter Selasky >> wrote: ... >>> Hi, >>> >>> The C_DIRECT_EXEC flag reduces task switching overhead, that you don't >>> have >>> to wakeup a thread to wak

Re: Timing issue with Dummynet on high kernel timer interrupt

2015-11-06 Thread Hans Petter Selasky
On 11/06/15 09:50, Luigi Rizzo wrote: On Fri, Nov 6, 2015 at 9:44 AM, Hans Petter Selasky wrote: On 11/06/15 01:08, Rasool Al-Saadi wrote: On Thursday, 5 November 2015 8:53 PM, Hans Petter Selasky wrote: On 11/05/15 00:44, Rasool Al-Saadi wrote: ... Removing C_HARDCLOCK reduces the prob

Re: Timing issue with Dummynet on high kernel timer interrupt

2015-11-06 Thread Luigi Rizzo
On Fri, Nov 6, 2015 at 9:44 AM, Hans Petter Selasky wrote: > On 11/06/15 01:08, Rasool Al-Saadi wrote: >> >> >> On Thursday, 5 November 2015 8:53 PM, Hans Petter Selasky wrote: >>> >>> >>> On 11/05/15 00:44, Rasool Al-Saadi wrote: ... >> Removing C_HARDCLOCK reduces the problem but doesn't solve

Re: Timing issue with Dummynet on high kernel timer interrupt

2015-11-06 Thread Hans Petter Selasky
On 11/06/15 01:08, Rasool Al-Saadi wrote: On Thursday, 5 November 2015 8:53 PM, Hans Petter Selasky wrote: On 11/05/15 00:44, Rasool Al-Saadi wrote: On Wednesday, 4 November 2015 12:34 AM, Hans Petter Selasky wrote: On 11/03/15 14:14, Rasool Al-Saadi wrote: Does anyone have thoughts on wha

Re: tap(4) and host-only networking between host and guest

2015-11-06 Thread Eugene Grosbein
On 06.11.2015 07:59, Craig Rodrigues wrote: > On Thu, Nov 5, 2015 at 4:36 PM, Miroslav Lachman <000.f...@quip.cz> wrote: > >> Eugene Grosbein wrote on 11/05/2015 18:06: >> >>> Yes, it is. And there is a solution: >>> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=165174 >>> >> >> I don't unders