From owner-freebsd-current@FreeBSD.ORG Thu Nov 1 17:11:27 2007 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8E9FB16A469 for ; Thu, 1 Nov 2007 17:11:27 +0000 (UTC) (envelope-from ianf@clue.co.za) Received: from munchkin.clue.co.za (munchkin.clue.co.za [66.219.59.160]) by mx1.freebsd.org (Postfix) with ESMTP id 6504113C4BB for ; Thu, 1 Nov 2007 17:11:27 +0000 (UTC) (envelope-from ianf@clue.co.za) DomainKey-Signature: a=rsa-sha1; q=dns; c=simple; s=20070313; d=clue.co.za; h=Received:Received:Received:To:Subject:From:X-Attribution:Date:Message-Id; b=pr9ZTMOeRkTwjtfBhMmQjYmgHMoMSte244akpoY4QyS4SKPwG6RyTcrRVA+u96Om62pnq8UjWPnb3os6KLQiYEmbI92bzVJ0NNq96PekHX0i/Z3CnyoNBx3561ThdQtoZ8Ej0Gjl2GbuzpUdtEMjA6uBiwjA5TSR6mIytp+5EDpsLuVx2TAl/ttpeMGKERpEyPjUq9okGtOo2EIQF/lLzcBoeGg+j9+DQSXLGGckDBbi6Yti3onnux7f1Yk/+3yv; Received: from uucp by munchkin.clue.co.za with local-rmail (Exim 4.67) (envelope-from ) id 1InaGM-0001z1-F0 for current@freebsd.org; Thu, 01 Nov 2007 13:39:10 +0000 Received: from ianf.clue.co.za ([10.0.0.6] helo=clue.co.za) by urchin.clue.co.za with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.66) (envelope-from ) id 1InaFQ-0002vT-Lq for current@freebsd.org; Thu, 01 Nov 2007 13:38:12 +0000 Received: from localhost ([127.0.0.1] helo=clue.co.za) by clue.co.za with esmtp (Exim 4.68 (FreeBSD)) (envelope-from ) id 1InaFP-0002HC-Sx for current@freebsd.org; Thu, 01 Nov 2007 15:38:11 +0200 To: current@freebsd.org From: Ian FREISLICH X-Attribution: BOFH Date: Thu, 01 Nov 2007 15:38:11 +0200 Message-Id: Cc: Subject: setitimer() odd timing 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, 01 Nov 2007 17:11:27 -0000 Hi I've got a issue that I noticed recently. When I set an alarm() or use setitimer() the signal delivery is delayed somewhat. I'm not sure if it's that the signal is delayed or if it's just that the timer runs slowly. I am using ITIMER_REAL. It's pretty linear over 1 to 60 (asked for) seconds translating them into 3.7 real seconds: [apple] ~ # time sleep 5 real 0m18.542s user 0m0.000s sys 0m0.001s [apple] ~ # time sleep 10 real 0m37.081s user 0m0.000s sys 0m0.001s [apple] ~ # time sleep 60 real 3m42.468s user 0m0.000s sys 0m0.001s The hardware in question is an Apple MacBook Pro. FWIW, I don't notice this on other i386 based hardware that I have. It affects things like ping, cron, atrun and xclock but not gettimeofday(). I'm not sure where to start looking. If someone points me at what needs instrumenting, I'll see if I can narrow the problem space. Ian -- Ian Freislich