From owner-freebsd-current Wed Jun 3 23:53:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA12233 for freebsd-current-outgoing; Wed, 3 Jun 1998 23:53:59 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from critter.freebsd.dk (critter.freebsd.dk [195.8.129.14]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA12208 for ; Wed, 3 Jun 1998 23:53:50 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.8.7/8.8.5) with ESMTP id IAA14709; Thu, 4 Jun 1998 08:51:54 +0200 (CEST) To: "Richard S. Straka" cc: current@FreeBSD.ORG Subject: Re: strange behavior with signal latencies In-reply-to: Your message of "Wed, 03 Jun 1998 22:56:51 PDT." <35763722.C34EEF4E@home.com> Date: Thu, 04 Jun 1998 08:51:53 +0200 Message-ID: <14707.896943113@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <35763722.C34EEF4E@home.com>, "Richard S. Straka" writes: >I wrote a small test program to look at latencies of user space >processes waking up on the delivery of signals. Hi Richard, This is very interesting work. The time keeping code in -current is entirely new, so it is not a given that it is actually a latency, it could be a genuine bug... A few pointers: 1. Use clock_gettime(2) on -current, then you get nanoseconds (-stable cannot do that, it will just give you microseconds * 1000). 2. Do you have ntpd enabled on either machine ? 3. Try to do the "/dev/io" trick and wiggle a line on your printerport and then use a 'scope or counter to verify your data. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." "ttyv0" -- What UNIX calls a $20K state-of-the-art, 3D, hi-res color terminal To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message