From owner-freebsd-current@FreeBSD.ORG Thu Jun 16 07:04:32 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 507D116A41C for ; Thu, 16 Jun 2005 07:04:32 +0000 (GMT) (envelope-from tataz@tataz.chchile.org) Received: from postfix3-1.free.fr (postfix3-1.free.fr [213.228.0.44]) by mx1.FreeBSD.org (Postfix) with ESMTP id 127E643D49 for ; Thu, 16 Jun 2005 07:04:31 +0000 (GMT) (envelope-from tataz@tataz.chchile.org) Received: from tatooine.tataz.chchile.org (vol75-8-82-233-239-98.fbx.proxad.net [82.233.239.98]) by postfix3-1.free.fr (Postfix) with ESMTP id 4417B173496; Thu, 16 Jun 2005 09:04:30 +0200 (CEST) Received: by tatooine.tataz.chchile.org (Postfix, from userid 1000) id DC227407E; Thu, 16 Jun 2005 09:04:45 +0200 (CEST) Date: Thu, 16 Jun 2005 09:04:45 +0200 From: Jeremie Le Hen To: "M. Warner Losh" Message-ID: <20050616070445.GD2239@obiwan.tataz.chchile.org> References: <20050615231823.GB2239@obiwan.tataz.chchile.org> <20050615.212446.29494502.imp@bsdimp.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050615.212446.29494502.imp@bsdimp.com> User-Agent: Mutt/1.5.9i Cc: freebsd-current@freebsd.org, jeremie@le-hen.org Subject: Re: incorrect ping(8) interval with powerd(8) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 Jun 2005 07:04:32 -0000 Hi Warner, > : %%% > : jarjarbinks:root# sysctl hw.acpi.acline > : hw.acpi.acline: 1 > : jarjarbinks:root# sysctl dev.cpu.0.freq > : dev.cpu.0.freq: 1735 > : jarjarbinks:root# time ping -qc 2 192.168.1.1 > : PING 192.168.1.1 (192.168.1.1): 56 data bytes > : > : --- 192.168.1.1 ping statistics --- > : 2 packets transmitted, 2 packets received, 0% packet loss > : round-trip min/avg/max/stddev = 0.266/0.269/0.271/0.002 ms > : > : real 0m1.003s > : user 0m0.001s > : sys 0m0.001s > : > : jarjarbinks:root# sysctl hw.acpi.acline > : hw.acpi.acline: 0 > : jarjarbinks:root# sysctl dev.cpu.0.freq > : dev.cpu.0.freq: 216 > : jarjarbinks:root# time ping -qc 2 192.168.1.1 > : PING 192.168.1.1 (192.168.1.1): 56 data bytes > : > : --- 192.168.1.1 ping statistics --- > : 2 packets transmitted, 2 packets received, 0% packet loss > : round-trip min/avg/max/stddev = 0.637/0.814/0.991/0.177 ms > : > : real 0m2.252s > : user 0m0.004s > : sys 0m0.021s > : %%% > : > : I check ping(8) source code and it appears it uses select(8) to wait > : the desired amount of time. I don't think this is the intended > : behaviour. Where does this bug (feature?) come from ? > > Those numbers look about right for a 200MHz CPU. May you delve into this a little bit more please ? The ping(8) manual page states that the -i flags makes ping(8) to wait a given couple of seconds. If I use the flags "-i 1", I expect ECHO Requests to be sent with one second between each, whatever the AC line status is. (Note that I didn't explicitely specified "-i 1" in the above example, but this doesn't change the behaviour.) Thank you. Regards, -- Jeremie Le Hen < jeremie at le-hen dot org >< ttz at chchile dot org >