linux-kernel - Re: [PATCH RFC 1/3] Add a trigger API for efficient non-blocking waiting

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: <200808251053.49033.rusty@rustcorp.com.au>
Date:	Mon, 25 Aug 2008 10:53:48 +1000
From:	Rusty Russell <rusty@...tcorp.com.au>
To:	Andrew Morton <akpm@...ux-foundation.org>
Cc:	Jeremy Fitzhardinge <jeremy@...p.org>, mingo@...e.hu,
	jens.axboe@...cle.com, a.p.zijlstra@...llo.nl, cborntra@...ibm.com,
	linux-kernel@...r.kernel.org, arjan@...radead.org
Subject: Re: [PATCH RFC 1/3] Add a trigger API for efficient non-blocking waiting

On Thursday 21 August 2008 05:25:46 Andrew Morton wrote:
> If stop_machine() is the _only_ problematic callsite and we reasonably
> expect that no new ones will pop up then sure, a
> stop_machine()-specific fix might be appropriate.
>
> Otherwise, sure, we'd need to loko at something more general.

The reason I'm interested is that we have 331 cpu_relax() calls outside the 
arch trees.  That seems like a lot, and I wonder if what they really want is
a spinpletion.

Cheers,
Rusty.
--
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/