From: "Steve Wise" <swise-7bPotxP6k4+P2YhJcF5u+vpXobYPEAuW@public.gmane.org>
To: 'Tatyana Nikolova'
<Tatyana.E.Nikolova-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
'Roland Dreier' <roland-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
Cc: john.s.lacombe-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org,
peter.p.waskiewicz.jr-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org,
sean.hefty-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org,
linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: RE: [PATCH 0/3] RDMA/core: iWARP Port Mapper Overview
Date: Fri, 2 May 2014 10:35:17 -0500 [thread overview]
Message-ID: <008b01cf661c$1e7957e0$5b6c07a0$@opengridcomputing.com> (raw)
In-Reply-To: <20140326220718.GA8784@TENIKOLO-MOBL1>
Any review comments on this?
> -----Original Message-----
> From: Tatyana Nikolova [mailto:Tatyana.E.Nikolova-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org]
> Sent: Wednesday, March 26, 2014 5:07 PM
> To: Roland Dreier
> Cc: john.s.lacombe-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org; swise-7bPotxP6k4+P2YhJcF5u+vpXobYPEAuW@public.gmane.org;
> peter.p.waskiewicz.jr-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org; sean.hefty-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org; linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
> Subject: [PATCH 0/3] RDMA/core: iWARP Port Mapper Overview
>
>
> Hello All,
>
> This patch series adds iWARP Port Mapper (IWPM) Version 2 support
> in RDMA/core, RDMA/nes driver and RDMA/cxgb4 driver.
> The iWARP Port Mapper implementation is based on the port mapper specification
> section in the Sockets Direct Protocol paper -
> http://www.rdmaconsortium.org/home/draft-pinkerton-iwarp-sdp-v1.0.pdf
>
> Existing iWARP RDMA providers use the same IP address as the native TCP/IP
> stack when creating RDMA connections. They need to ensure a mechanism to claim
> the TCP ports used for RDMA connections, thereby preventing TCP port collisions
> when other host applications are consuming TCP ports. The iWARP Port Mapper
> provides a standard mechanism to accomplish this. Without this service it is
> possible for RDMA application to bind/listen on the same port which is already
> being used by native TCP host application. If that happens the incoming TCP
> connection data can be passed to the RDMA stack with error.
>
> The iWARP Port Mapper solution doesn't contain any changes to the existing
> network stack in the kernel space. All the changes are contained with the
> infiniband tree and also in user space.
>
> The iWARP Port Mapper service is implemented as a user space daemon process.
> Interested readers could look at the source code of the IWPM service located at
> http://git.openfabrics.org/git?p=~tnikolova/libiwpm-1.0.0/.git;a=summary
>
> The iWARP driver (port mapper client) sends to the IWPM service the local IP
> address and TCP port it has received from the RDMA application, when starting a
> connection. The IWPM service performs a socket bind from user space to get
> an available TCP port, called a mapped port, and communicates it back to the
> client. In that sense, the IWPM service is used to map the TCP port, which the
> RDMA application uses to any port available from the host TCP port space. The
> mapped ports are used in iWARP RDMA connections to avoid collisions with native
> TCP stack which is aware that these ports are taken. When an RDMA connection
> using a mapped port is terminated, the client notifies the IWPM service, which
> then releases the TCP port.
>
> The message exchange between the IWPM service and the iWARP drivers
> (between user space and kernel space) is implemented using netlink sockets.
>
> This patch series adds iWarp driver support for sending/receiving/parsing
> netlink messages, to make the communication with the IWPM service possible.
>
> This is the second submission for the iWarp Port Mapper and
> we have considered and incorporated feedback after the first submission
> to improve the IWPM Version 2 patch series.
>
> The following items are improvements and fixes to IWPM V2:
>
> 1) The IWPM functionality, common for both iWarp drivers (nes and cxgb4)
> is refactored from the drivers source files and is moved to new shared
> files in infiniband/core which are compiled as part of the iw_cm module.
>
> 2) Hash table data structure is implemented to store the drivers mapping
> information and enable efficient searching. (Hash table implementation
> is based on original work by Vipul Pandya)
>
> 3) Fix for a timer bug is provided as the unnecessary timer scheduling is
> removed.
>
> The patches are built against Roland's infiniband tree for-next branch.
>
> Thank you,
>
> Tatyana Nikolova (2):
> RDMA/core: Add support for iWarp Port Mapper V2 user space service
> RDMA/nes: Add support for iWarp Port Mapper V2 user space service
> Steve Wise (1):
> RDMA/cxgb4: Add support for iWarp Port Mapper V2 user space service
>
> drivers/infiniband/core/Makefile | 2 +-
> drivers/infiniband/core/cma.c | 3 +-
> drivers/infiniband/core/iwpm_msg.c | 691 ++++++++++++++++++++++++++++++++
> drivers/infiniband/core/iwpm_util.c | 609 ++++++++++++++++++++++++++++
> drivers/infiniband/core/iwpm_util.h | 238 +++++++++++
> drivers/infiniband/core/netlink.c | 18 +-
> drivers/infiniband/hw/cxgb4/cm.c | 180 +++++++--
> drivers/infiniband/hw/cxgb4/device.c | 81 ++++-
> drivers/infiniband/hw/cxgb4/iw_cxgb4.h | 44 ++
> drivers/infiniband/hw/nes/nes.c | 25 ++-
> drivers/infiniband/hw/nes/nes.h | 3 +
> drivers/infiniband/hw/nes/nes_cm.c | 320 ++++++++++++---
> drivers/infiniband/hw/nes/nes_cm.h | 12 +-
> include/rdma/iw_portmap.h | 199 +++++++++
> include/rdma/rdma_netlink.h | 23 +-
> include/uapi/rdma/rdma_netlink.h | 96 +++++-
> 16 files changed, 2431 insertions(+), 113 deletions(-)
> create mode 100644 drivers/infiniband/core/iwpm_msg.c
> create mode 100644 drivers/infiniband/core/iwpm_util.c
> create mode 100644 drivers/infiniband/core/iwpm_util.h
> create mode 100644 include/rdma/iw_portmap.h
--
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:[~2014-05-02 15:35 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-26 22:07 [PATCH 0/3] RDMA/core: iWARP Port Mapper Overview Tatyana Nikolova
2014-05-02 15:35 ` Steve Wise [this message]
2014-05-20 1:10 ` Roland Dreier
[not found] ` <CAL1RGDWNr53rXY_o2X7R76aVHtAH_EnK6DZk19N5fGoW1pOAdQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-05-20 13:45 ` Steve Wise
2014-05-20 17:46 ` Nikolova, Tatyana E
2014-06-03 20:20 ` Or Gerlitz
2014-05-20 7:47 ` Or Gerlitz
[not found] ` <001a01cf7431$f6d41f30$e47c5d90$@opengridcomputing.com>
2014-05-20 13:59 ` Or Gerlitz
2014-06-08 19:34 ` Or Gerlitz
[not found] ` <CAJZOPZ+E0sX6-_tT2DrbLvRvrHWvEcO5KtMGwZqhuoQeTqrrMg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-06-09 14:46 ` Steve Wise
2014-06-09 16:51 ` Jason Gunthorpe
[not found] ` <20140609165105.GB1816-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
2014-06-09 18:10 ` Christoph Lameter
[not found] ` <alpine.DEB.2.10.1406091307230.9663-gkYfJU5Cukgdnm+yROfE0A@public.gmane.org>
2014-06-09 18:13 ` Steve Wise
2014-06-09 18:28 ` Christoph Lameter
[not found] ` <alpine.DEB.2.10.1406091326430.9663-gkYfJU5Cukgdnm+yROfE0A@public.gmane.org>
2014-06-09 18:32 ` Steve Wise
2014-06-09 18:12 ` Steve Wise
2014-06-09 18:42 ` Jason Gunthorpe
[not found] ` <2ABFA3E36CBB794685BFBA191CC1964952C605CB@FMSMSX105.amr.corp.intel.com>
[not found] ` <2ABFA3E36CBB794685BFBA191CC1964952C605CB-AtyAts71sc9qS6EAlXoojrfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2014-06-10 0:08 ` FW: " PJ Waskiewicz
[not found] ` <CAEmgqz2HtEJ1ho0rS4xR7ud6YgFfeAvR8uD8MgPjVhw=E9PFEg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-06-10 6:10 ` Or Gerlitz
[not found] ` <5396A145.90504-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org>
2014-06-10 7:03 ` PJ Waskiewicz
2014-06-10 16:52 ` Jason Gunthorpe
[not found] ` <20140610165246.GA12951-ePGOBjL8dl3ta4EC/59zMFaTQe2KTcn/@public.gmane.org>
2014-06-10 19:30 ` PJ Waskiewicz
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='008b01cf661c$1e7957e0$5b6c07a0$@opengridcomputing.com' \
--to=swise-7bpotxp6k4+p2yhjcf5u+vpxobypeauw@public.gmane.org \
--cc=Tatyana.E.Nikolova-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=john.s.lacombe-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=peter.p.waskiewicz.jr-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=roland-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
--cc=sean.hefty-ral2JQCrhuEAvxtiuMwx3w@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.