From: Will Deacon <will.deacon@arm.com>
To: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
Cc: Michael Cree <mcree@orcon.net.nz>,
parri.andrea@gmail.com, linux-alpha@vger.kernel.org,
peterz@infradead.org, rth@twiddle.net, ink@jurassic.park.msu.ru,
mattst88@gmail.com, mark.rutland@arm.com
Subject: Re: Do any Alpha systems include InfiniBand?
Date: Mon, 23 Oct 2017 18:16:25 +0100 [thread overview]
Message-ID: <20171023171625.GF6222@arm.com> (raw)
In-Reply-To: <20171023171312.GL3659@linux.vnet.ibm.com>
On Mon, Oct 23, 2017 at 10:13:12AM -0700, Paul E. McKenney wrote:
> On Mon, Oct 23, 2017 at 09:59:21PM +1300, Michael Cree wrote:
> > On Fri, Oct 20, 2017 at 12:48:32PM -0700, Paul E. McKenney wrote:
> > > Do any of the DEC Alpha systems that run recent kernels have InfiniBand?
> > > Given my understanding of the history, I believe the answer to be "no".
> >
> > I am not aware of any Alpha systems with InfiniBand.
>
> Very good, then we need not worry about any Alpha-related consequences
> of removing smp_read_barrier_depends() invocations from the InfiniBand
> driver. ;-)
But maybe make that driver depend on !CONFIG_ALPHA, so as to avoid planting
any subtle ordering bugs?
Will
next prev parent reply other threads:[~2017-10-23 17:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-20 19:48 Do any Alpha systems include InfiniBand? Paul E. McKenney
2017-10-20 20:00 ` Matt Turner
2017-10-20 20:15 ` Paul E. McKenney
2017-10-23 8:59 ` Michael Cree
2017-10-23 17:13 ` Paul E. McKenney
2017-10-23 17:16 ` Will Deacon [this message]
2017-10-23 18:01 ` Paul E. McKenney
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=20171023171625.GF6222@arm.com \
--to=will.deacon@arm.com \
--cc=ink@jurassic.park.msu.ru \
--cc=linux-alpha@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mattst88@gmail.com \
--cc=mcree@orcon.net.nz \
--cc=parri.andrea@gmail.com \
--cc=paulmck@linux.vnet.ibm.com \
--cc=peterz@infradead.org \
--cc=rth@twiddle.net \
/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;
as well as URLs for NNTP newsgroup(s).