Re: Direct io on block device has performance regression on 2.6.xkernel

[Andi Kleen]

"Chen, Kenneth W" <kenneth.w.chen@xxxxxxxxx> writes:
>
> Just to clarify here, these data need to be taken at grain of salt. A
> high count in _spin_unlock_* functions do not automatically points to
> lock contention.  It's one of the blind spot syndrome with timer based
> profile on ia64.  There are some lock contentions in 2.6 kernel that
> we are staring at.  Please do not misinterpret the number here.

Why don't you use oprofileÂ>? It uses NMIs and can profile "inside" 
interrupt disabled sections.

-Andi
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/