linux-kernel - Re: [PATCH] locking/rwlocks: clean up of qrwlock

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: <20150106101311.GM29390@twins.programming.kicks-ass.net>
Date:	Tue, 6 Jan 2015 11:13:11 +0100
From:	Peter Zijlstra <peterz@...radead.org>
To:	Baoquan He <bhe@...hat.com>
Cc:	Waiman Long <waiman.long@...com>, mingo@...hat.com,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] locking/rwlocks: clean up of qrwlock

On Tue, Jan 06, 2015 at 05:25:42PM +0800, Baoquan He wrote:
> Hi all,
> 
> Thanks for reviewing. 
> 
> Do you have any other concerns about this small change?

I just don't see any point in making the code worse for the 1 arch that
actually uses it. If there were other archs using it and for them the
code generation would be negatively impacted (they'd actually generate
more core because of it) it might be worth looking at.
--
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/