Re: Linux Kernel Markers - performance characterization with large IO load on large-ish system

!MAILaRCHIVE_VOTE_RePLACE
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
To: Alan D. Brunelle <Alan.Brunelle@...>
Cc: Mathieu Desnoyers <mathieu.desnoyers@...>, <linux-kernel@...>, btrace <linux-btrace@...>, Jens Axboe <jens.axboe@...>, Andrew Morton <akpm@...>
Date: Sunday, October 7, 2007 - 3:32 pm

* Alan D. Brunelle <Alan.Brunelle@hp.com> wrote:


actually, the pure marker overhead seems to be a regression:


why isnt the marker near zero-cost as it should be? (as long as they are 
enabled but are not in actual use) 2% increase is _ALOT_. That's the 
whole point of good probes: they do not slow down the normal kernel.

_Worst case_ it should be at most a few instructions overhead but that 
does not explain the ~2% wall-clock time regression you measured here.

So there's something wrong going on - either markers have unacceptably 
high cost, or the measurement is not valid.

	Ingo
-
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
Re: Linux Kernel Markers - performance characterization with..., Alan D. Brunelle, (Tue Sep 25, 10:58 am)
Re: Linux Kernel Markers - performance characterization with..., Mathieu Desnoyers, (Tue Sep 25, 1:13 pm)
Re: Linux Kernel Markers - performance characterization with..., Alan D. Brunelle, (Wed Sep 26, 11:28 am)
Re: Linux Kernel Markers - performance characterization with..., Ingo Molnar, (Sun Oct 7, 3:32 pm)