From owner-freebsd-net@freebsd.org  Wed Nov  4 23:44:24 2015
Return-Path: <owner-freebsd-net@freebsd.org>
Delivered-To: freebsd-net@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 24EFDA26418
 for <freebsd-net@mailman.ysv.freebsd.org>;
 Wed,  4 Nov 2015 23:44:24 +0000 (UTC)
 (envelope-from ralsaadi@swin.edu.au)
Received: from iport1.cc.swin.edu.au (iport1.cc.swin.edu.au [136.186.0.49])
 by mx1.freebsd.org (Postfix) with ESMTP id B08BC117B
 for <freebsd-net@freebsd.org>; Wed,  4 Nov 2015 23:44:23 +0000 (UTC)
 (envelope-from ralsaadi@swin.edu.au)
X-IronPort-AV: E=Sophos;i="5.20,245,1444654800"; d="scan'208";a="14570228"
Received: from gsp-ex03.ds.swin.edu.au (HELO outlook.swin.edu.au)
 ([136.186.126.19])
 by iport1.cc.swin.edu.au with ESMTP; 05 Nov 2015 10:44:16 +1100
Received: from GSP-EX02.ds.swin.edu.au ([169.254.2.2]) by
 gsp-ex03.ds.swin.edu.au ([169.254.3.127]) with mapi id 14.03.0248.002; Thu, 5
 Nov 2015 10:44:15 +1100
From: Rasool Al-Saadi <ralsaadi@swin.edu.au>
To: Hans Petter Selasky <hps@selasky.org>, "freebsd-net@freebsd.org"
 <freebsd-net@freebsd.org>
Subject: RE: Timing issue with Dummynet on high kernel timer interrupt
Thread-Topic: Timing issue with Dummynet on high kernel timer interrupt
Thread-Index: AdEWOVE5DoAlkzqPQWaBZ8ln4esVd///TXiA//0UVtA=
Date: Wed, 4 Nov 2015 23:44:14 +0000
Message-ID: <6545444AE21C2749939E637E56594CEA3C0DE7FF@gsp-ex02.ds.swin.edu.au>
References: <6545444AE21C2749939E637E56594CEA3C0DCCC4@gsp-ex02.ds.swin.edu.au>
 <5638B7B5.3030802@selasky.org>
In-Reply-To: <5638B7B5.3030802@selasky.org>
Accept-Language: en-AU, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [136.186.126.11]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-BeenThere: freebsd-net@freebsd.org
X-Mailman-Version: 2.1.20
Precedence: list
List-Id: Networking and TCP/IP with FreeBSD <freebsd-net.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-net>,
 <mailto:freebsd-net-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-net/>
List-Post: <mailto:freebsd-net@freebsd.org>
List-Help: <mailto:freebsd-net-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-net>,
 <mailto:freebsd-net-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 04 Nov 2015 23:44:24 -0000


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 what we can test next to narrow down the
> root-cause of these unusual timing jumps?
>=20
> You might also want to test the "projects/hps_head" branch, which uses a =
bit
> different callout implementation.

Thanks Hans for your suggestion.
I have tried "projects/hps_head" branch and the result is better (number of=
 spikes is less than in the master branch). However, the problem still exis=
ts on the same timer interrupt frequencies (>3000 in my case). You can see =
in this graph https://goo.gl/photos/C2Mqx4xhMQuzxWnz6 the RTT spikes still =
there.

Do you have any further suggestions?=20

Regards,
Rasool

> --HPS
> _______________________________________________
> freebsd-net@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-net
> To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org"