Re: [PATCH] possible fix for the runtime going backwards warnings
- From: Andrey Chernov <ache@xxxxxxxxxxx>
- Date: Wed, 22 Feb 2006 16:25:09 +0300
On Tue, Feb 21, 2006 at 09:36:46PM -0500, Kris Kennaway wrote:
On Tue, Feb 21, 2006 at 10:47:04AM -0500, John Baldwin wrote:
The latest round of calcru() changes accidentally changed calccru() to use the
wrong rusage_ext structure (p->p_rux vs p->p_crux) when calculating usage
times for children. The patch fixes calccru() to use p->p_crux again. It
also moves the ruadd() in exit1() even later in the function so that it takes
the dying thread's last time slice into account. Please test it and let me
know if it makes the messages go away (or if it makes things worse!) Thanks!
http://www.FreeBSD.org/~jhb/patches/calccru.patch
I think you committed this already, right?
I'm still getting calcru spam on the 3 SMP machines that I upgraded
with fresh sources:
I too (but less than before patch), UP machine:
Feb 22 03:37:45 pobrecita kernel: calcru: runtime went backwards from 292542 usec to 292537 usec for pid 29 (pagezero)
Feb 22 03:37:45 pobrecita kernel: u 0:0/0 s 38:292542/292537 i 0:0/0
--
http://ache.pp.ru/
Attachment:
pgpiT8TMt4eT2.pgp
Description: PGP signature
- References:
- [PATCH] possible fix for the runtime going backwards warnings
- From: John Baldwin
- Re: [PATCH] possible fix for the runtime going backwards warnings
- From: Kris Kennaway
- [PATCH] possible fix for the runtime going backwards warnings
- Prev by Date: Re: proposed /sbin/init permission change
- Next by Date: Re: Bad code in rcorder(8) (Was: Re: New RCorder: abi loaded too late)
- Previous by thread: Re: [PATCH] possible fix for the runtime going backwards warnings
- Next by thread: Re: [PATCH] possible fix for the runtime going backwards warnings
- Index(es):
Relevant Pages
|
|
