From owner-freebsd-net@freebsd.org  Sat Nov  7 11:51:26 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 60916A27BB7
 for <freebsd-net@mailman.ysv.freebsd.org>;
 Sat,  7 Nov 2015 11:51:26 +0000 (UTC)
 (envelope-from brde@optusnet.com.au)
Received: from mail110.syd.optusnet.com.au (mail110.syd.optusnet.com.au
 [211.29.132.97]) by mx1.freebsd.org (Postfix) with ESMTP id 10BCC10AA
 for <freebsd-net@freebsd.org>; Sat,  7 Nov 2015 11:51:25 +0000 (UTC)
 (envelope-from brde@optusnet.com.au)
Received: from c211-30-166-197.carlnfd1.nsw.optusnet.com.au
 (c211-30-166-197.carlnfd1.nsw.optusnet.com.au [211.30.166.197])
 by mail110.syd.optusnet.com.au (Postfix) with ESMTPS id 7BF28783992;
 Sat,  7 Nov 2015 22:51:15 +1100 (AEDT)
Date: Sat, 7 Nov 2015 22:51:14 +1100 (EST)
From: Bruce Evans <brde@optusnet.com.au>
X-X-Sender: bde@besplex.bde.org
To: Hans Petter Selasky <hps@selasky.org>
cc: Bruce Evans <brde@optusnet.com.au>, Rasool Al-Saadi <ralsaadi@swin.edu.au>,
 Luigi Rizzo <rizzo@iet.unipi.it>, 
 "freebsd-net@freebsd.org" <freebsd-net@freebsd.org>
Subject: Re: Timing issue with Dummynet on high kernel timer interrupt
In-Reply-To: <563DD6B2.8010607@selasky.org>
Message-ID: <20151107223816.D1837@besplex.bde.org>
References: <6545444AE21C2749939E637E56594CEA3C0DCCC4@gsp-ex02.ds.swin.edu.au>
 <5638B7B5.3030802@selasky.org>
 <6545444AE21C2749939E637E56594CEA3C0DE7FF@gsp-ex02.ds.swin.edu.au>
 <563B2703.5080402@selasky.org>
 <6545444AE21C2749939E637E56594CEA3C0E0BD9@gsp-ex02.ds.swin.edu.au>
 <563C6864.2090907@selasky.org>
 <CA+hQ2+hm2z0MkB-8w5xJM7+iz13r_ZjwmpZBnb30_D_48gaf-w@mail.gmail.com>
 <563C786C.1050305@selasky.org>
 <CA+hQ2+j0WiGgzV119M1ZQiXP5Z7fq7deVxDPkOhvTc7hpTETKw@mail.gmail.com>
 <563CC186.9000807@selasky.org>
 <6545444AE21C2749939E637E56594CEA3C0E1B79@gsp-ex02.ds.swin.edu.au>
 <20151107162915.A893@besplex.bde.org> <563DD6B2.8010607@selasky.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
X-Optus-CM-Score: 0
X-Optus-CM-Analysis: v=2.1 cv=R4L+YolX c=1 sm=1 tr=0
 a=KA6XNC2GZCFrdESI5ZmdjQ==:117 a=PO7r1zJSAAAA:8 a=JzwRw_2MAAAA:8
 a=kj9zAlcOel0A:10 a=0G27pUAqrrk60t1OlWMA:9 a=CjuIK1q_8ugA:10
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: Sat, 07 Nov 2015 11:51:26 -0000

On Sat, 7 Nov 2015, Hans Petter Selasky wrote:

> On 11/07/15 07:19, Bruce Evans wrote:
>> I don't know if CTLFLAG_RWTUN with SYSCTL_PROC() actually works for all
>> types, but it is used with CTLFLAG_STRING for kern.corefile.  This is
>> another bogus undocumented tunable.  It is better documented as a sysctl
>> than most since it is old so it is documented in sysctl(8).  It is not
>> documented as a tunable there of course.  It is also not documented as
>> a tunable in core(5).
>
> SYSCTL_PROC() works with RWTUN from /boot/loader.conf, as long as the 
> procedure callback handles early calls during boot.

Hmm, that would be messy if it wants to do hardware stuff like
sysctl_kern_eventtimer_periodic() does.

Timercounters only have 1 MI tunable
(sysctl_kern_timecounter_adjprecision).  It has a (cold) check to avoid
doing too much.

Bruce