mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Arjan van de Ven <arjan@infradead.org>
To: Andreas Mohr <andi@rhlx01.fht-esslingen.de>
Cc: Andrew Morton <akpm@osdl.org>,
	Nick Piggin <nickpiggin@yahoo.com.au>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH -mm 1/6] cpu_relax(): interrupt.h
Date: Wed, 21 Jun 2006 23:04:20 +0200	[thread overview]
Message-ID: <1150923860.3057.116.camel@laptopd505.fenrus.org> (raw)
In-Reply-To: <20060621205932.GA22516@rhlx01.fht-esslingen.de>

On Wed, 2006-06-21 at 22:59 +0200, Andreas Mohr wrote:
> Add cpu_relax() to tasklet_unlock_wait() loop.
> 
> 
> I kept barrier() since it is said to still be required, in various older
> postings.

cpu_relax() includes a barrier always, per definition.
(simply because anywhere you would use cpu_relax() you would also put a
barrier)



      reply	other threads:[~2006-06-21 21:04 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-21 20:59 Andreas Mohr
2006-06-21 21:04 ` Arjan van de Ven [this message]

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=1150923860.3057.116.camel@laptopd505.fenrus.org \
    --to=arjan@infradead.org \
    --cc=akpm@osdl.org \
    --cc=andi@rhlx01.fht-esslingen.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nickpiggin@yahoo.com.au \
    /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

all inboxes | Powered by JetHome®