From: Sean Hefty <mshefty@ichips.intel.com>
To: "Kanevsky, Arkady" <Arkady.Kanevsky@netapp.com>
Cc: Steve Wise <swise@opengridcomputing.com>,
Sean Hefty <sean.hefty@intel.com>,
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: Fri, 28 Sep 2007 14:34:56 -0700 [thread overview]
Message-ID: <46FD7380.6050107@ichips.intel.com> (raw)
In-Reply-To: <C98692FD98048C41885E0B0FACD9DFB805187762@exnane01.hq.netapp.com>
Kanevsky, Arkady wrote:
> Exactly,
> it forces the burden on administrator.
> And one will be forced to try one mount for iWARP and it does not
> work issue another one TCP or UDP if it fails.
> Yack!
>
> And server will need to listen on different IP address and simple
> * will not work since it will need to listen in two different domains.
The server already has to call listen twice. Once for the rdma_cm and
once for sockets. Similarly on the client side, connect must be made
over rdma_cm or sockets. I really don't see any impact on the
application for this approach.
We just end up separating the port space based on networking addresses,
rather than keeping the problem at the transport level. If you have an
alternate approach that will be accepted upstream, feel free to post it.
- Sean
next prev parent reply other threads:[~2007-09-28 21:35 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 ` [ofa-general] [PATCH v3] iw_cxgb3: Support "iwarp-only"interfacesto " Sean Hefty
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 [this message]
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=46FD7380.6050107@ichips.intel.com \
--to=mshefty@ichips.intel.com \
--cc=Arkady.Kanevsky@netapp.com \
--cc=general@lists.openfabrics.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=rdreier@cisco.com \
--cc=sean.hefty@intel.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).