On Wed, May 09, 2018 at 01:36:08PM +0200, Martin Pieuchot wrote:
> On 08/05/18(Tue) 18:03, Martin Pieuchot wrote:
> > Diff below, gypped from jmatthew@, allows us to see how much time CPUs
> > spend spinning on a mutex or on the KERNEL_LOCK().
> >
> > On my sparc64 with 16 CPUs, top(1) now reports
On Wed, May 09, 2018 at 01:36:08PM +0200, Martin Pieuchot wrote:
> > To keep it simple, systat(1) vmstat view now shows the spinning time instead
> > of the nice time.
Could the nice time added to user there? I interpret this line
that the sum should be 100%. Anyway, that can be changed later.
On Wed, May 09, 2018 at 01:36:08PM +0200, Martin Pieuchot wrote:
> On 08/05/18(Tue) 18:03, Martin Pieuchot wrote:
> > Diff below, gypped from jmatthew@, allows us to see how much time CPUs
> > spend spinning on a mutex or on the KERNEL_LOCK().
> >
> > On my sparc64 with 16 CPUs, top(1) now reports
On 08/05/18(Tue) 18:03, Martin Pieuchot wrote:
> Diff below, gypped from jmatthew@, allows us to see how much time CPUs
> spend spinning on a mutex or on the KERNEL_LOCK().
>
> On my sparc64 with 16 CPUs, top(1) now reports:
>
> 16 CPUs: 16.8% user, 0.0% nice, 9.2% sys, 49.4% spin, 0.1% intr,
Diff below, gypped from jmatthew@, allows us to see how much time CPUs
spend spinning on a mutex or on the KERNEL_LOCK().
On my sparc64 with 16 CPUs, top(1) now reports:
16 CPUs: 16.8% user, 0.0% nice, 9.2% sys, 49.4% spin, 0.1% intr, 24.5% idle
And systat(1) CPU view:
CPUUser
