From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Michael Cree <mcree@orcon.net.nz>
Cc: Miklos Szeredi <miklos@szeredi.hu>,
James.Bottomley@HansenPartnership.com, benh@kernel.crashing.org,
dhowells@redhat.com, linux-kernel@vger.kernel.org,
linux-arch@vger.kernel.org
Subject: Re: memory barrier question
Date: Wed, 22 Sep 2010 11:41:44 -0700 [thread overview]
Message-ID: <20100922184144.GA11741@linux.vnet.ibm.com> (raw)
In-Reply-To: <20100921145910.GA3358@linux.vnet.ibm.com>
On Tue, Sep 21, 2010 at 07:59:10AM -0700, Paul E. McKenney wrote:
> On Mon, Sep 20, 2010 at 01:40:55PM -0700, Paul E. McKenney wrote:
> > On Tue, Sep 21, 2010 at 08:26:14AM +1200, Michael Cree wrote:
> > > On 21/09/10 06:25, Paul E. McKenney wrote:
> > > >But do we really care about Alpha anymore? (I can see it now... The
> > > >Alpha portion of the kernel tree moves to staging...)
> > >
> > > I do.
> > >
> > > Sent from my Compaq Alpha XP1000 :-)
> >
> > In that case, an smp_read_barrier_depends() or rcu_dereference() is
> > also required...
>
> Wait a minute... I finally got a chance to look up the system. This
> system has only a single Alpha CPU, right?
>
> If so, just build a UP kernel and be happy. No need to worry about
> any of these SMP issues.
>
> So, an alternative proposal -- support only UP kernels on Alpha. ;-)
And there do seem to be some SMP Alpha systems still in use:
http://www.alphalinux.org/wiki/index.php/User:Armin76/HW_list
Thanx, Paul
next prev parent reply other threads:[~2010-09-22 18:41 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-15 14:36 memory barrier question Miklos Szeredi
2010-09-15 19:12 ` Rafael J. Wysocki
2010-09-16 11:55 ` David Howells
2010-09-16 13:42 ` Miklos Szeredi
2010-09-16 13:42 ` Miklos Szeredi
2010-09-16 13:42 ` Miklos Szeredi
2010-09-16 14:30 ` David Howells
2010-09-16 15:03 ` Paul E. McKenney
2010-09-16 16:06 ` Miklos Szeredi
2010-09-16 16:37 ` Paul E. McKenney
2010-09-16 16:56 ` Miklos Szeredi
2010-09-16 17:09 ` James Bottomley
2010-09-16 17:17 ` Miklos Szeredi
2010-09-16 17:40 ` James Bottomley
2010-09-17 21:49 ` Benjamin Herrenschmidt
2010-09-17 23:12 ` Paul E. McKenney
2010-09-19 2:47 ` Benjamin Herrenschmidt
2010-09-19 15:26 ` Paul E. McKenney
2010-09-19 20:15 ` Miklos Szeredi
2010-09-19 21:59 ` Paul E. McKenney
2010-09-20 0:58 ` James Bottomley
2010-09-20 1:29 ` Paul E. McKenney
2010-09-20 16:01 ` Miklos Szeredi
2010-09-20 18:25 ` Paul E. McKenney
2010-09-20 18:25 ` Paul E. McKenney
2010-09-20 18:57 ` Paul E. McKenney
2010-09-20 20:26 ` Michael Cree
2010-09-20 20:40 ` Paul E. McKenney
2010-09-21 14:59 ` Paul E. McKenney
2010-09-22 18:41 ` Paul E. McKenney [this message]
2010-09-18 1:12 ` Alan Cox
2010-09-16 16:50 ` Jamie Lokier
2010-09-16 16:18 ` Peter Zijlstra
2010-09-16 16:18 ` Peter Zijlstra
2010-09-16 17:59 ` David Howells
-- strict thread matches above, loose matches on Subject: below --
2010-09-20 10:34 George Spelvin
2010-10-29 13:23 Memory " Tetsuo Handa
2010-10-29 15:09 ` Paul E. McKenney
2010-10-30 5:48 ` Tetsuo Handa
2010-10-30 6:11 ` Eric Dumazet
2010-10-30 12:40 ` Tetsuo Handa
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=20100922184144.GA11741@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=benh@kernel.crashing.org \
--cc=dhowells@redhat.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mcree@orcon.net.nz \
--cc=miklos@szeredi.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.