From: Brian Pomerantz <bapper@piratehaven.org>
To: yiding_wang@agilent.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: InfiniBand Project
Date: Fri, 5 Jan 2001 15:44:46 -0800 [thread overview]
Message-ID: <20010105154446.A11669@skull.piratehaven.org> (raw)
In-Reply-To: <FEEBE78C8360D411ACFD00D0B747797101128D68@xsj02.sjs.agilent.com>
In-Reply-To: <FEEBE78C8360D411ACFD00D0B747797101128D68@xsj02.sjs.agilent.com>
There is a possibility I could work on here at LLNL. My group has
been talking about investigating Infiniband and we figured Linux would
be a good spot to start with it. The ASCI Purple machine (100 TFLOPS)
will probably use IB for it's I/O network, though there is obviously
no commitment to is yet as this machines delivery date is a ways away.
We need to start looking at it soon so we know how well we can
integrate it into our environment.
BAPper
On Fri, Jan 05, 2001 at 04:06:24PM -0700, yiding_wang@agilent.com wrote:
> Has anyone started IB support project for Linux yet? Particularly I am
> interested in OS support and verbs layer from Linux side. I am involved in
> an IB product on HCA and TCA side. Current solution will be emulating scsi
> but eventually all IB component is required. I noticed that kernel 2.4.0
> only has IB class defined.
>
> Many thanks!
>
> Eddie
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> Please read the FAQ at http://www.tux.org/lkml/
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
prev parent reply other threads:[~2001-01-05 23:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-05 23:06 yiding_wang
2001-01-05 23:44 ` Brian Pomerantz [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=20010105154446.A11669@skull.piratehaven.org \
--to=bapper@piratehaven.org \
--cc=linux-kernel@vger.kernel.org \
--cc=yiding_wang@agilent.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®