linux-kernel - Re: [PATCH 2/4, v2] x86: enlightenment for ticket spin locks

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: <1277888180.1868.84.camel@laptop>
Date:	Wed, 30 Jun 2010 10:56:20 +0200
From:	Peter Zijlstra <peterz@...radead.org>
To:	Jan Beulich <JBeulich@...ell.com>
Cc:	jeremy.fitzhardinge@...rix.com, mingo@...e.hu, tglx@...utronix.de,
	Ky Srinivasan <KSrinivasan@...ell.com>,
	linux-kernel@...r.kernel.org, hpa@...or.com
Subject: Re: [PATCH 2/4, v2] x86: enlightenment for ticket spin locks - Xen
 implementation

On Wed, 2010-06-30 at 09:52 +0100, Jan Beulich wrote:
> > why is that a rwlock?, those things are useless.
> 
> Because potentially each CPU's lock gets acquired for reading during
> unlock, while only the locking CPU's one needs to be acquired for
> writing during lock. 

Can you say: scalability nightmare? but then its Xen code so who cares..

/me pretends he never saw it
--
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/