linux-kernel - Re: [patch 0/2] x86,pat: Reduce contention on the memtype

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <87wrx2for5.fsf@basil.nowhere.org>
Date:	Wed, 24 Mar 2010 03:16:14 +0100
From:	Andi Kleen <andi@...stfloor.org>
To:	holt@....com
Cc:	Ingo Molnar <mingo@...hat.com>, "H. Peter Anvin" <hpa@...or.com>,
	Thomas Gleixner <tglx@...utronix.de>,
	Venkatesh Pallipadi <venkatesh.pallipadi@...il.com>,
	Suresh Siddha <suresh.b.siddha@...el.com>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	x86@...nel.org, Rafael Wysocki <rjw@...ell.com>
Subject: Re: [patch 0/2] x86,pat: Reduce contention on the memtype_lock -V4

holt@....com writes:

> 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@...ux.intel.com -- Speaking for myself only.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/