From: "Sean Hefty" <sean.hefty@intel.com>
To: "'Kanevsky, Arkady'" <Arkady.Kanevsky@netapp.com>,
"Sean Hefty" <mshefty@ichips.intel.com>,
"Steve Wise" <swise@opengridcomputing.com>
Cc: <netdev@vger.kernel.org>, <rdreier@cisco.com>,
<linux-kernel@vger.kernel.org>, <general@lists.openfabrics.org>
Subject: RE: [ofa-general] [PATCH v3] iw_cxgb3: Support "iwarp-only"interfacesto avoid 4-tuple conflicts.
Date: Thu, 27 Sep 2007 12:11:49 -0700 [thread overview]
Message-ID: <000101c8013a$41b374f0$a7cc180a@amr.corp.intel.com> (raw)
In-Reply-To: <C98692FD98048C41885E0B0FACD9DFB805187514@exnane01.hq.netapp.com>
>What is the model on how client connects, say for iSCSI,
>when client and server both support, iWARP and 10GbE or 1GbE,
>and would like to setup "most" performant "connection" for ULP?
For the "most" performance connection, the ULP would use IB, and all these
problems go away. :)
This proposal is for each iwarp interface to have its own IP address. Clients
would need an iwarp usable address of the server and would connect using
rdma_connect(). If that call (or rdma_resolve_addr/route) fails, the client
could try connecting using sockets, aoi, or some other interface. I don't see
that Steve's proposal changes anything from the client's perspective.
- Sean
next prev parent reply other threads:[~2007-09-27 19:11 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-23 20:36 [ofa-general] [PATCH v3] iw_cxgb3: Support "iwarp-only" interfaces to avoid 4-tuple conflicts Steve Wise
2007-09-26 19:02 ` Steve Wise
2007-09-27 18:38 ` Sean Hefty
2007-09-27 18:56 ` [ofa-general] [PATCH v3] iw_cxgb3: Support "iwarp-only" interfacesto " Kanevsky, Arkady
2007-09-27 19:11 ` Sean Hefty [this message]
2007-09-27 20:19 ` [ofa-general] [PATCH v3] iw_cxgb3: Support"iwarp-only"interfacesto " Kanevsky, Arkady
2007-09-28 19:46 ` Steve Wise
2007-09-28 20:36 ` Kanevsky, Arkady
2007-09-28 21:27 ` Steve Wise
2007-09-28 21:34 ` Sean Hefty
2007-10-01 12:34 ` [ofa-general] [PATCH v3] iw_cxgb3: Support"iwarp-only"interfacestoavoid " Kanevsky, Arkady
2007-10-08 18:03 ` [ofa-general] [PATCH v3] iw_cxgb3: Support"iwarp-only"interfacesto avoid " Steve Wise
2007-09-27 19:25 ` [ofa-general] [PATCH v3] iw_cxgb3: Support "iwarp-only" interfaces to " Steve Wise
2007-09-27 20:14 ` Sean Hefty
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='000101c8013a$41b374f0$a7cc180a@amr.corp.intel.com' \
--to=sean.hefty@intel.com \
--cc=Arkady.Kanevsky@netapp.com \
--cc=general@lists.openfabrics.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mshefty@ichips.intel.com \
--cc=netdev@vger.kernel.org \
--cc=rdreier@cisco.com \
--cc=swise@opengridcomputing.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).