holt@sgi.com writes:

quoted text
> Tracking memtype on x86 uses a single global spin_lock for either reading
> or changing the memory type.  This includes changes made to page flags
> which is perfectly parallel.
>
> Part one of the patchset makes the page-based tracking use cmpxchg
> without a need for a lock.
>
> Part two of the patchset converts the spin_lock into a read/write lock.

I'm curious: in what workloads did you see contention?

For any scalability patches it would be always good to have a description
of the workload.

-Andi

-- 
ak@linux.intel.com -- Speaking for myself only.
--
unsubscribe notice
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/