]
Sent: Tuesday, October 07, 2008 7:58 PM
To:
Cc: freebsd-questions@freebsd.org; [EMAIL PROTECTED];
[EMAIL PROTECTED]
Subject: Re: kernel profiling: spinlock_exit consumes 36% CPU time.
On Tue, Oct 07, 2008 at 07:44:00PM +0800, wrote:
Hi, folks,
I did kernel profiling when a single
Many thanks for the information.
Could we say that interrupt handlers consumed ~36% execution time?
Is this number too high? Is it possible that we abuse the use of critical
sections in kernel?
Looking forward to your options. Many thanks.
Qiu Jian
On Tuesday 07 October 2008 07:44:00 am 邱剑
On Wednesday 08 October 2008 03:51:48 am 邱剑 wrote:
Many thanks for the information.
Could we say that interrupt handlers consumed ~36% execution time?
Is this number too high? Is it possible that we abuse the use of critical
sections in kernel?
I think whether or not it is high depends on
On Tue, 7 Oct 2008, John Baldwin wrote:
On Tuesday 07 October 2008 07:44:00 am wrote:
Hi, folks,
I did kernel profiling when a single thread client sends UDP packets to a
single thread server on the same machine.
In the output kernel profile, the first few kernel functions that consumes
On Tue, Oct 07, 2008 at 07:44:00PM +0800, wrote:
Hi, folks,
I did kernel profiling when a single thread client sends UDP packets to a
single thread server on the same machine.
In the output kernel profile, the first few kernel functions that consumes
the most CPU time are listed
邱剑 wrote:
Hi, folks,
[...]
spinlocks disable interrupts so the profiling interrupt is held off
from the
moment that the spinlock is entered to the moment it is exited, and all
of that time is attributed to spinlock_exit().
so that this tells you that 3% of your time is spent under spinlocks
On Tuesday 07 October 2008 07:44:00 am 邱剑 wrote:
Hi, folks,
I did kernel profiling when a single thread client sends UDP packets to a
single thread server on the same machine.
In the output kernel profile, the first few kernel functions that consumes
the most CPU time are listed below:
Hi, folks,
I did kernel profiling when a single thread client sends UDP packets to a
single thread server on the same machine.
In the output kernel profile, the first few kernel functions that consumes
the most CPU time are listed below:
granularity: each sample hit covers 16 byte(s) for
