Date: Wed, 10 Jun 1998 18:14:28 +0200 From: Poul-Henning Kamp <phk@critter.freebsd.dk> To: Bruce Evans <bde@zeta.org.au> Cc: current@FreeBSD.ORG, jb@cimlogic.com.au, jdp@polstra.com, rb@gid.co.uk Subject: Re: Spurious SIGXCPU Message-ID: <25281.897495268@critter.freebsd.dk> In-Reply-To: Your message of "Thu, 11 Jun 1998 01:49:01 %2B1000." <199806101549.BAA29945@godzilla.zeta.org.au>
next in thread | previous in thread | raw e-mail | index | archive | help
In message <199806101549.BAA29945@godzilla.zeta.org.au>, Bruce Evans writes: >>>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 ? > >Probably. I fixed it by clearing switchtime.tv_sec in fork_trampoline() >and am now trying to figure out why that works :-). huh ??? -- 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?25281.897495268>