On Tue, 2007-11-27 at 20:57 +1100, Paul Mackerras wrote: > Johannes Berg writes: > > > Contrary to what I claimed later in the thread, my 64-bit powerpc box > > (quad-core G5) doesn't suffer from this problem. > > > > Does anybody have any idea? I don't even know how to debug it further. > > I see it on my G4 powerbook. However, a compute-bound task runs just > as fast (i.e. completes in the same elapsed time) as on older kernels, > so it does look like it is just an accounting problem. If the CPU was > really spending more than half its time servicing hardware interrupts, > the task should take more than twice as long to complete. Exactly. So where do I look for the accounting bug? johannes
Attachment:
signature.asc
Description: This is a digitally signed message part
- References:
- time accounting problem (powerpc only?)
- From: Johannes Berg <[email protected]>
- Re: time accounting problem (powerpc only?)
- From: Johannes Berg <[email protected]>
- Re: time accounting problem (powerpc only?)
- From: Paul Mackerras <[email protected]>
- time accounting problem (powerpc only?)
- Prev by Date: Re: time accounting problem (powerpc only?)
- Next by Date: Re: [PATCH] kexec: force x86_64 arches to boot kdump kernels on boot cpu
- Previous by thread: Re: time accounting problem (powerpc only?)
- Next by thread: Re: time accounting problem (powerpc only?)
- Index(es):