From: Roland Dreier <roland@topspin.com>
To: Karen Shaeffer <shaeffer@neuralscape.com>
Cc: netdev@oss.sgi.com, linux-kernel@vger.kernel.org,
openib-general@openib.org
Subject: Re: [PATCH][v5][0/24] Latest IB patch queue
Date: Tue, 28 Dec 2004 17:36:12 -0800 [thread overview]
Message-ID: <52hdm5j377.fsf@topspin.com> (raw)
In-Reply-To: <20041229012817.GA18863@synapse.neuralscape.com> (Karen Shaeffer's message of "Tue, 28 Dec 2004 17:28:17 -0800")
Roland> I think sparc64 is the only such platform where InfiniBand
Roland> is likely to be of much interest. However I'll check out
Roland> all of arch/ and send patches to hook up
Roland> drivers/infiniband/ to the relevant maintainers once IB
Roland> makes it upstream.
Karen> I am interested in Infiniband with x86_64 Opterons.
OK, the current code should work well for you -- x86_64 is probably
the most-tested architecture.
"such platform[s]" in my comment above referred to architectures where
arch/xxx/Kconfig does _not_ include drivers/Kconfig;
arch/x86_64/Kconfig does include that file. So no change is required
to use the current IB patches on x86_64. I believe the only
architectures that both support PCI and do not include drivers/Kconfig
in their arch Kconfig are arm, sparc, sparc64 and v850. Perhaps I'm
wrong, but of those four architectures, sparc64 seems to be the only
one where there would be any interest in using IB.
- Roland
prev parent reply other threads:[~2004-12-29 1:36 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-28 5:50 [PATCH][v5][0/24] Latest IB patch queue Roland Dreier
2004-12-28 5:50 ` [PATCH][v5][1/24] Add core InfiniBand support (public headers) Roland Dreier
2004-12-28 5:50 ` [PATCH][v5][2/24] Add core InfiniBand support Roland Dreier
2004-12-28 5:50 ` [PATCH][v5][3/24] Hook up drivers/infiniband Roland Dreier
2004-12-28 5:50 ` [PATCH][v5][4/24] Add InfiniBand MAD (management datagram) support (public headers) Roland Dreier
2004-12-28 5:50 ` [PATCH][v5][5/24] Add InfiniBand MAD (management datagram) support Roland Dreier
2004-12-28 5:50 ` [PATCH][v5][6/24] Add InfiniBand MAD (management datagram) support (private headers) Roland Dreier
2004-12-28 5:51 ` [PATCH][v5][7/24] Add InfiniBand MAD SMI support Roland Dreier
2004-12-28 5:51 ` [PATCH][v5][8/24] Add InfiniBand SA (Subnet Administration) query support Roland Dreier
2004-12-28 5:51 ` [PATCH][v5][9/24] Add Mellanox HCA low-level driver Roland Dreier
2004-12-28 5:51 ` [PATCH][v5][10/24] Add Mellanox HCA low-level driver (midlayer interface) Roland Dreier
2004-12-28 5:51 ` [PATCH][v5][11/24] Add Mellanox HCA low-level driver (FW commands) Roland Dreier
2004-12-28 5:51 ` [PATCH][v5][12/24] Add Mellanox HCA low-level driver (EQ) Roland Dreier
2004-12-28 5:51 ` [PATCH][v5][13/24] Add Mellanox HCA low-level driver (initialization) Roland Dreier
2004-12-28 5:51 ` [PATCH][v5][14/24] Add Mellanox HCA low-level driver (QP/CQ) Roland Dreier
2004-12-28 5:51 ` [PATCH][v5][15/24] Add Mellanox HCA low-level driver (last bits) Roland Dreier
2004-12-28 5:51 ` [PATCH][v5][16/24] Add Mellanox HCA low-level driver (MAD) Roland Dreier
2004-12-28 5:51 ` [PATCH][v5][17/24] IPoIB IPv4 multicast Roland Dreier
2004-12-28 5:51 ` [PATCH][v5][18/24] IPoIB IPv6 support Roland Dreier
2004-12-28 5:51 ` [PATCH][v5][19/24] Add IPoIB (IP-over-InfiniBand) driver Roland Dreier
2004-12-28 5:51 ` [PATCH][v5][20/24] Add IPoIB multicast & partition code Roland Dreier
2004-12-28 5:51 ` [PATCH][v5][21/24] Add InfiniBand userspace MAD support Roland Dreier
2004-12-28 5:51 ` [PATCH][v5][22/24] Document InfiniBand ioctl use Roland Dreier
2004-12-28 5:51 ` [PATCH][v5][23/24] Add InfiniBand Documentation files Roland Dreier
2004-12-28 5:51 ` [PATCH][v5][24/24] InfiniBand MAINTAINERS entry Roland Dreier
2004-12-28 6:54 ` [PATCH][v5][0/24] Latest IB patch queue David S. Miller
2004-12-28 19:48 ` Roland Dreier
2004-12-28 22:17 ` David S. Miller
2004-12-28 23:24 ` Roland Dreier
2004-12-29 1:28 ` Karen Shaeffer
2004-12-29 1:36 ` Roland Dreier [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=52hdm5j377.fsf@topspin.com \
--to=roland@topspin.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@oss.sgi.com \
--cc=openib-general@openib.org \
--cc=shaeffer@neuralscape.com \
/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).