Re: aim7 performance regression by commit 5a50508 report from LKP

From: Ingo Molnar
Date: Tue Jan 29 2013 - 03:44:11 EST



* Yuanhan Liu <yuanhan.liu@xxxxxxxxxxxxxxx> wrote:

> [...]

Very nice measurements and analysis, thanks!

> As stated above, anybody can have a chance to own the lock in
> mutex once somebody release the lock. Well, there is only one
> to own the lock in rwsem write lock, and the one is known
> already: the one in the head of wait list. That would result
> to more contention in rwsem write lock case, especially if the
> one _will_ own the lock is not running now.

I think we should allow lock-steal between rwsem writers - that
will not hurt fairness as most rwsem fairness concerns relate to
reader vs. writer fairness.

Am I correct to assume that all relevant users in this workload
are down_write() users?

You can see the type of lock use in:

perf record -g
perf report

I bet that allowing rwsem writer lock-steal would improve other
workloads as well.

Thanks,

Ingo
--
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/