From: Masanori ITOH <marc@labs.fujitsu.com>
To: woody@co.intel.com
Cc: hozer@hozed.org, infiniband-general@lists.sourceforge.net,
linux-kernel@vger.kernel.org
Subject: Re: [Infiniband-general] Getting an Infiniband access layer in the linux kernel
Date: Tue, 03 Feb 2004 10:38:52 +0900 (JST) [thread overview]
Message-ID: <20040203.103852.74728002.marc@labs.fujitsu.com> (raw)
In-Reply-To: <F595A0622682C44DBBE0BBA91E56A5ED1C3662@orsmsx410.jf.intel.com>
Hello Folks,
Message-ID: <F595A0622682C44DBBE0BBA91E56A5ED1C3662@orsmsx410.jf.intel.com>
>
> We were waiting until we had some version of the InfiniBand code ported
> to 2.6 before
> asking for it to be included in the 2.6 kernel tree. Jerrie made the
> changes
> to the IB access layer to allow it to compile on 2.6, but it cannot yet
> be tested
> till we get a 2.6 driver from Mellanox.
Now, I'm testing a VPD for Fujitsu InfiniBand HCA card.
The VPD requires no special SDK such as VAPI of Mellanox.
In order to do that, I made some changes locally on IBAL and COMPLIB layers
based on the change set 1.207. I still have some problems, but opensm and
ipoib are working on linux-2.6.1 environment.
Robert, if you could make Jarrie's modification public at bkbits.net,
I can test the modification for 2.6 kernel using Fujitsu HCA.
Meanwhile, Mellanox is not the only supplier of InfiniBand HCA.
Fujitsu, Japan, also has InfiniBand HCA card with an original LSI
different from Tavor chip.
Thanks in advance,
Masanori
> I'd also like to hear from the linux-kernel folks on what we would need
> to
> do to get a basic InfiniBand access layer included in the 2.6 base.
>
> We'd also like to hear from Mellanox if they have any plans to provide
> an open
> source VPD driver anytime soon.
>
> woody
---
Masanori ITOH Grid Computing & Bioinformatics Lab., Fujitsu Labs. LTD.
e-mail: marc@labs.fujitsu.com
phone: +81-44-754-2628 (extension: 7112-6227)
FingerPrint: 55AF C562 E415 FB1A 8A3A 35D1 AB40 8A9D B8B1 99F8
next prev parent reply other threads:[~2004-02-03 1:38 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-02 23:58 Woodruff, Robert J
2004-02-03 0:56 ` Greg KH
2004-02-03 1:38 ` Masanori ITOH [this message]
2004-02-03 22:37 ` Troy Benjegerdes
2004-02-03 16:45 Woodruff, Robert J
2004-02-04 11:26 ` Masanori ITOH
2004-02-04 0:17 Woodruff, Robert J
2004-02-04 1:03 ` Greg KH
2004-02-04 2:01 Woodruff, Robert J
2004-02-04 4:08 ` Troy Benjegerdes
2004-02-04 4:53 Woodruff, Robert J
[not found] <C1B7430B33A4B14F80D29B5126C5E94703262582@orsmsx401.jf.intel.com>
2004-02-05 18:09 ` Greg KH
2004-02-05 18:31 [Infiniband-general] Getting an Infiniband access layer in the Linux kernel Tillier, Fabian
2004-02-05 18:40 ` Greg KH
2004-02-05 18:53 ` Randy.Dunlap
2004-02-07 2:54 ` Jamie Lokier
2004-02-05 18:34 [Infiniband-general] Getting an Infiniband access layer in the linux kernel Raj, Ashok
[not found] <33561BB7A415E04FBDC339D5E149C6E26C38FA@orsmsx405.jf.intel.com>
2004-02-05 18:55 ` Greg KH
2004-02-05 19:31 Raj, Ashok
2004-02-05 19:38 King, Steven R
2004-02-05 21:51 ` Greg KH
2004-02-05 19:44 [Infiniband-general] Getting an Infiniband access layer in the Linux kernel Tillier, Fabian
2004-02-05 20:16 ` Greg KH
2004-02-05 20:16 [Infiniband-general] Getting an Infiniband access layer in the linux kernel Woodruff, Robert J
2004-02-05 21:54 ` Greg KH
2004-02-06 23:20 ` Jamie Lokier
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=20040203.103852.74728002.marc@labs.fujitsu.com \
--to=marc@labs.fujitsu.com \
--cc=hozer@hozed.org \
--cc=infiniband-general@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=woody@co.intel.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
all inboxes | Powered by JetHome®