From: Rusty Russell <rusty@rustcorp.com.au>
To: Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH RFC 1/3] Add a trigger API for efficient non-blocking waiting
Date: Mon, 25 Aug 2008 10:53:48 +1000
User-Agent: KMail/1.9.9
Cc: Jeremy Fitzhardinge <jeremy@goop.org>, mingo@elte.hu,
       jens.axboe@oracle.com, a.p.zijlstra@chello.nl, cborntra@de.ibm.com,
       linux-kernel@vger.kernel.org, arjan@infradead.org
References: <48A70185.2020600@goop.org> <48AC6593.80505@goop.org> <20080820122546.6022d91d.akpm@linux-foundation.org>
In-Reply-To: <20080820122546.6022d91d.akpm@linux-foundation.org>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200808251053.49033.rusty@rustcorp.com.au>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 730
Lines: 18

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@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/