From: Sean Hefty <mshefty@ichips.intel.com>
To: David Miller <davem@davemloft.net>
Cc: swise@opengridcomputing.com, rdreier@cisco.com,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
general@lists.openfabrics.org
Subject: Re: [ofa-general] Re: [PATCH RFC] RDMA/CMA: Allocate PS_TCP ports from the host TCP port space.
Date: Thu, 09 Aug 2007 16:22:46 -0700 [thread overview]
Message-ID: <46BBA1C6.9010702@ichips.intel.com> (raw)
In-Reply-To: <20070809.145534.102938208.davem@davemloft.net>
> How about we just remove the RDMA stack altogether? I am not at all
> kidding. If you guys can't stay in your sand box and need to cause
> problems for the normal network stack, it's unacceptable. We were
> told all along the if RDMA went into the tree none of this kind of
> stuff would be an issue.
There are currently two RDMA solutions available. Each solution has
different requirements and uses the normal network stack differently.
Infiniband uses its own transport. iWarp runs over TCP.
We have tried to leverage the existing infrastructure where it makes sense.
> After TCP port reservation, what's next? It seems an at least
> bi-monthly event that the RDMA folks need to put their fingers
> into something else in the normal networking stack. No more.
Currently, the RDMA stack uses its own port space. This causes a
problem for iWarp, and is what Steve is looking for a solution for. I'm
not an iWarp guru, so I don't know what options exist. Can iWarp use
its own address family? Identify specific IP addresses for iWarp use?
Restrict iWarp to specific port numbers? Let the app control the
correct operation? I don't know.
Steve merely defined a problem and suggested a possible solution. He's
looking for constructive help trying to solve the problem.
- Sean
next prev parent reply other threads:[~2007-08-09 23:23 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-07 14:37 [PATCH RFC] RDMA/CMA: Allocate PS_TCP ports from the host TCP port space Steve Wise
2007-08-07 14:54 ` Evgeniy Polyakov
2007-08-07 15:06 ` Steve Wise
2007-08-07 15:39 ` Evgeniy Polyakov
2007-08-09 18:49 ` Steve Wise
2007-08-09 21:40 ` [ofa-general] " Sean Hefty
2007-08-09 21:55 ` David Miller
2007-08-09 23:22 ` Sean Hefty [this message]
2007-08-15 14:42 ` Steve Wise
2007-08-16 2:26 ` Jeff Garzik
2007-08-16 3:11 ` Roland Dreier
2007-08-16 3:27 ` [ofa-general] Re: [PATCH RFC] RDMA/CMA: Allocate PS_TCP portsfrom " Sean Hefty
2007-08-16 13:43 ` [ofa-general] Re: [PATCH RFC] RDMA/CMA: Allocate PS_TCP ports from " Tom Tucker
2007-08-16 21:17 ` David Miller
2007-08-17 19:52 ` Roland Dreier
2007-08-17 21:27 ` David Miller
2007-08-17 23:31 ` Roland Dreier
2007-08-18 0:00 ` David Miller
2007-08-18 5:23 ` Roland Dreier
2007-08-18 6:44 ` David Miller
2007-08-19 7:01 ` [ofa-general] Re: [PATCH RFC] RDMA/CMA: Allocate PS_TCP portsfrom " Sean Hefty
2007-08-19 7:23 ` David Miller
2007-08-19 17:33 ` [ofa-general] Re: [PATCH RFC] RDMA/CMA: Allocate PS_TCPportsfrom " Felix Marti
2007-08-19 19:32 ` David Miller
2007-08-19 19:49 ` Felix Marti
2007-08-19 23:04 ` David Miller
2007-08-20 0:32 ` Felix Marti
2007-08-20 0:40 ` David Miller
2007-08-20 0:47 ` Felix Marti
2007-08-20 1:05 ` David Miller
2007-08-20 1:41 ` Felix Marti
2007-08-20 11:07 ` Andi Kleen
2007-08-20 16:26 ` Felix Marti
2007-08-20 19:16 ` Rick Jones
2007-08-20 9:43 ` Evgeniy Polyakov
2007-08-20 16:53 ` Felix Marti
2007-08-20 18:10 ` Andi Kleen
2007-08-20 19:02 ` Felix Marti
2007-08-20 20:18 ` Thomas Graf
2007-08-20 20:33 ` Andi Kleen
2007-08-20 20:33 ` Patrick Geoffray
2007-08-21 4:21 ` Felix Marti
2007-08-19 23:27 ` Andi Kleen
2007-08-19 23:12 ` David Miller
2007-08-20 1:45 ` Felix Marti
2007-08-20 0:18 ` Herbert Xu
2007-08-21 1:16 ` [ofa-general] Re: [PATCH RFC] RDMA/CMA: Allocate PS_TCP ports from " Roland Dreier
2007-08-21 6:58 ` David Miller
2007-08-28 19:38 ` Roland Dreier
2007-08-28 20:43 ` David Miller
2007-10-08 21:54 ` Steve Wise
2007-10-09 13:44 ` James Lentini
2007-10-10 21:01 ` Sean Hefty
2007-10-10 23:04 ` David Miller
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=46BBA1C6.9010702@ichips.intel.com \
--to=mshefty@ichips.intel.com \
--cc=davem@davemloft.net \
--cc=general@lists.openfabrics.org \
--cc=linux-kernel@vger.kernel.org \
--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