iwpmd(8) - f34

1iwpmd(8)                             iwpmd                            iwpmd(8)
2
3
4

NAME

6       iwpmd - port mapping services for iWARP.
7

SYNOPSIS

9       iwpmd
10

DESCRIPTION

12       The  iWARP Port Mapper Daemon provides a user space service (iwpmd) for
13       the iWarp drivers to claim tcp ports through the standard socket inter‐
14       face.
15
16       The  kernel space support for the port mapper is part of the iw_cm mod‐
17       ule.  The ib_core module includes netlink support, which is used by the
18       port mapper clients to exchange messages with iwpmd. Both modules iw_cm
19       and ib_core need to be loaded in order for the libiwpm service to start
20       successfully.
21

IWARP PORT MAPPING DETAILS

23       The iWARP Port Mapper implementation is based on the port mapper speci‐
24       fication section in the Sockets Direct Protocol: http://www.rdmaconsor‐
25       tium.org/home/draft-pinkerton-iwarp-sdp-v1.0.pdf
26
27       Existing  iWARP  RDMA  providers  use the same IP address as the native
28       TCP/IP stack when creating RDMA connections.  They need a mechanism  to
29       claim  the TCP ports used for RDMA connections to prevent TCP port col‐
30       lisions when other host applications use TCP  ports.   The  iWARP  Port
31       Mapper  provides a standard mechanism to accomplish this.  Without this
32       service it is possible for RDMA application to bind/listen on the  same
33       port  which  is  already being used by native TCP host application.  If
34       that happens the incoming TCP connection data can be passed to the RDMA
35       stack with error.
36
37       The  iWARP  Connection  Manager  (port mapper client) sends to the IWPM
38       service the local IP address and TCP port it has received from the RDMA
39       application,  when  starting a connection.  The IWPM service performs a
40       socket bind from user space to get an  available  TCP  port,  called  a
41       mapped  port,  and  communicates it back to the client.  In that sense,
42       the IWPM service is used to map the TCP port, which the  RDMA  applica‐
43       tion  uses  to  any  port  available  from the host TCP port space. The
44       mapped ports are used in iWARP RDMA  connections  to  avoid  collisions
45       with  native  TCP stack which is aware that these ports are taken. When
46       an RDMA connection using a mapped port is terminated, the client  noti‐
47       fies the IWPM service, which then releases the TCP port.
48
49       The  message  exchange  between  iwpmd and the iWARP Connection Manager
50       (between user space and kernel  space)  is  implemented  using  netlink
51       sockets.
52

OPTIONS

54       -s, --systemd Enable systemd integration.
55

SIGNALS

57       SIGUSR1 will force a dump of the current mappings to the system message
58       log.
59
60       SIGTERM/SIGHUP will force iwpmd to exit.
61

FILES

63       /etc/iwpmd.conf
64