public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Rusty Russell <rusty@rustcorp.com.au>
To: Andrew Morton <akpm@linux-foundation.org>
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
Subject: Re: [PATCH RFC 1/3] Add a trigger API for efficient non-blocking waiting
Date: Mon, 25 Aug 2008 10:53:48 +1000	[thread overview]
Message-ID: <200808251053.49033.rusty@rustcorp.com.au> (raw)
In-Reply-To: <20080820122546.6022d91d.akpm@linux-foundation.org>

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.

  parent reply	other threads:[~2008-08-25  4:00 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-16 16:34 [PATCH RFC 1/3] Add a trigger API for efficient non-blocking waiting Jeremy Fitzhardinge
2008-08-16 17:47 ` Arjan van de Ven
2008-08-17 23:02 ` Randy Dunlap
2008-08-20  6:21 ` Andrew Morton
2008-08-20 18:42   ` Jeremy Fitzhardinge
2008-08-20 19:25     ` Andrew Morton
2008-08-20 20:14       ` Jeremy Fitzhardinge
2008-08-25  0:53       ` Rusty Russell [this message]
2008-08-28 12:27 ` Christian Borntraeger

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200808251053.49033.rusty@rustcorp.com.au \
    --to=rusty@rustcorp.com.au \
    --cc=a.p.zijlstra@chello.nl \
    --cc=akpm@linux-foundation.org \
    --cc=arjan@infradead.org \
    --cc=cborntra@de.ibm.com \
    --cc=jens.axboe@oracle.com \
    --cc=jeremy@goop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox