public inbox for netdev@vger.kernel.org 
 help / color / mirror / Atom feed
From: David Howells <dhowells@redhat•com>
To: Chris Snook <csnook@redhat•com>
Cc: dhowells@redhat•com, linux-kernel@vger•kernel.org,
	linux-arch@vger•kernel.org, torvalds@linux-foundation•org,
	netdev@vger•kernel.org, akpm@linux-foundation•org, ak@suse•de,
	heiko.carstens@de•ibm.com, davem@davemloft•net,
	schwidefsky@de•ibm.com, wensong@linux-vs•org, horms@verge•net.au,
	wjiang@resilience•com, cfriesen@nortel•com, zlynx@acm•org,
	rpjday@mindspring•com, jesper.juhl@gmail•com
Subject: Re: [PATCH 6/24] make atomic_read() behave consistently on frv
Date: Sat, 11 Aug 2007 09:47:51 +0100	[thread overview]
Message-ID: <7680.1186822071@redhat.com> (raw)
In-Reply-To: <46BCC26B.6080600@redhat.com>

Chris Snook <csnook@redhat•com> wrote:

> cpu_relax() contains a barrier, so it should do the right thing.  For non-smp
> architectures, I'm concerned about interacting with interrupt handlers.  Some
> drivers do use atomic_* operations.

I'm not sure that actually answers my question.  Why not smp_rmb()?

David

  parent reply	other threads:[~2007-08-11  8:47 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-09 13:41 [PATCH 6/24] make atomic_read() behave consistently on frv Chris Snook
2007-08-09 16:54 ` Chris Snook
2007-08-10  9:23   ` David Howells
2007-08-10 19:54     ` Chris Snook
2007-08-11  0:54       ` Herbert Xu
2007-08-11  4:29         ` Paul E. McKenney
2007-08-13  5:15           ` Herbert Xu
2007-08-13  6:03             ` Paul E. McKenney
2007-08-14  5:34               ` Nick Piggin
2007-08-14  7:26                 ` Herbert Xu
2007-08-14 17:01                 ` Paul E. McKenney
2007-08-14 22:01                   ` Arnd Bergmann
2007-08-14 22:43                     ` Paul E. McKenney
2007-08-15 13:29                       ` Arnd Bergmann
2007-08-15 15:06                         ` Michael Buesch
2007-08-15 13:30                   ` Nick Piggin
2007-08-15 20:15                     ` Paul E. McKenney
2007-08-16  1:09                       ` Nick Piggin
2007-08-16  2:27                         ` Paul E. McKenney
2007-08-11  8:47       ` David Howells [this message]
2007-08-13  6:44         ` Chris Snook
2007-08-14  5:42           ` Nick Piggin
2007-08-15 18:51             ` Segher Boessenkool
2007-08-15 19:18               ` Paul E. McKenney
2007-08-15 19:46                 ` Segher Boessenkool
2007-08-15 19:59                   ` Paul E. McKenney
2007-08-15 20:13                     ` Segher Boessenkool
2007-08-15 20:38                       ` Paul E. McKenney
2007-08-15 21:15                         ` Segher Boessenkool
2007-08-16  1:20                           ` Nick Piggin

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=7680.1186822071@redhat.com \
    --to=dhowells@redhat$(echo .)com \
    --cc=ak@suse$(echo .)de \
    --cc=akpm@linux-foundation$(echo .)org \
    --cc=cfriesen@nortel$(echo .)com \
    --cc=csnook@redhat$(echo .)com \
    --cc=davem@davemloft$(echo .)net \
    --cc=heiko.carstens@de$(echo .)ibm.com \
    --cc=horms@verge$(echo .)net.au \
    --cc=jesper.juhl@gmail$(echo .)com \
    --cc=linux-arch@vger$(echo .)kernel.org \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=netdev@vger$(echo .)kernel.org \
    --cc=rpjday@mindspring$(echo .)com \
    --cc=schwidefsky@de$(echo .)ibm.com \
    --cc=torvalds@linux-foundation$(echo .)org \
    --cc=wensong@linux-vs$(echo .)org \
    --cc=wjiang@resilience$(echo .)com \
    --cc=zlynx@acm$(echo .)org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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