From owner-freebsd-current Wed Jun 10 08:27:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA23746 for freebsd-current-outgoing; Wed, 10 Jun 1998 08:27:40 -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 IAA23741 for ; Wed, 10 Jun 1998 08:27:37 -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 RAA25120; Wed, 10 Jun 1998 17:25:39 +0200 (CEST) To: Bruce Evans cc: jb@cimlogic.com.au, rb@gid.co.uk, current@FreeBSD.ORG, jdp@polstra.com Subject: Re: Spurious SIGXCPU In-reply-to: Your message of "Wed, 10 Jun 1998 23:23:46 +1000." <199806101323.XAA21805@godzilla.zeta.org.au> Date: Wed, 10 Jun 1998 17:25:39 +0200 Message-ID: <25118.897492339@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199806101323.XAA21805@godzilla.zeta.org.au>, Bruce Evans writes: >Apparently the background process makes it more likely for the foreground >process to appear to take a negative amount of time. > >Another sign of the bug is that accounting for rapid context switches >is broken again: > > $ time ./fork-benchmark 10000 > 6.10 real 0.01 user 8.33 sys if you make it always call microuptime(&p->p_switchtime); after cpu_switch() in kern_synch, does that make it any different ? -- 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