From: Roland Dreier <rdreier-FYB4Gu1CFyUAvxtiuMwx3w@public.gmane.org>
To: javed-If5XQcfNmg0@public.gmane.org
Cc: linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: patch for non-ib network
Date: Sun, 22 Nov 2009 20:19:52 -0800 [thread overview]
Message-ID: <adabpit6ffb.fsf@roland-alpha.cisco.com> (raw)
In-Reply-To: <Pine.LNX.4.62.0911201915430.25859-NG0XCrj25/kh/ldBx82aDQ@public.gmane.org> (javed-If5XQcfNmg0@public.gmane.org's message of "Fri, 20 Nov 2009 19:54:41 +0530 (IST)")
> is it possible to add a patch in ofed release for non-ib networks?
> we've integrated ofed with 'paramnet-3' a 10Gbps system area
> network. currently IPoIB is working fine. more details can be provided
> if required.
I think rather than worrying about OFED, you're better off working on
getting your drivers integrated in the mainline kernel.
However if you just have IPoIB working, and your fabric is not IB, then
I think you might be better off implementing IP-over-paramnet-3 and
avoiding the complexity of the RDMA stack. Unless paramnet-3 is RDMA-like?
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2009-11-23 4:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-20 14:24 patch for non-ib network javed-If5XQcfNmg0
[not found] ` <Pine.LNX.4.62.0911201915430.25859-NG0XCrj25/kh/ldBx82aDQ@public.gmane.org>
2009-11-20 16:13 ` Christoph Lameter
2009-11-23 4:19 ` Roland Dreier [this message]
[not found] ` <adabpit6ffb. fsf@roland-alpha.cisco.com>
[not found] ` <adabpit6ffb.fsf-BjVyx320WGW9gfZ95n9DRSW4+XlvGpQz@public.gmane.org>
2009-11-23 13:27 ` javed-If5XQcfNmg0
[not found] ` <Pine.LNX.4.62.0911231138530.24997-NG0XCrj25/kh/ldBx82aDQ@public.gmane.org>
2009-11-23 19:11 ` Roland Dreier
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=adabpit6ffb.fsf@roland-alpha.cisco.com \
--to=rdreier-fyb4gu1cfyuavxtiumwx3w@public.gmane.org \
--cc=javed-If5XQcfNmg0@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
/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