Physical Network Id Example; D.2.8 Software Exploitation Of Smc-R - IBM z13s Technical Manual

Figure D-7 shows the three physically separate networks defined.
Switch A
Network A
Figure D-7 Physical network ID example
Sample IOCP FUNCTION statement
Example D-1 shows one sample IOCP FUNCTION configuration to define an RoCE Express
adapter shared between LPARs.
Example D-1 IOCP FUNCTION statements
FUNCTION FID=05,PCHID=100,PART=((LP08),(LP09)),VF=1,TYPE=ROCE,PNETID=(PNETA,PNETB)
FUNCTION FID=06,PCHID=12C,PART=((LP08),(LP09)),VF=1,TYPE=ROCE,PNETID=(PNETA,PNETB)
FUNCTION FID=07,PCHID=100,PART=((LP12),(LP06)),VF=2,TYPE=ROCE,PNETID=(PNETA,PNETB)
FUNCTION FID=08,PCHID=12C,PART=((LP12),(LP06)),VF=2,TYPE=ROCE,PNETID=(PNETA,PNETB)
This example has these characteristics:
PNETID array identifies the network that the ports are associated with. Thus, all FIDs on a
RoCE adapter that are associated with the same PCHID must have the same PNETID for
each port.
10GbE RoCE Express Functions for LPAR 08 are reconfigurable to LP 09 with access to
two networks.
10GbE RoCE Express Functions for LPAR 12 are reconfigurable to LP 06 with access to
two networks.
Physical RoCE Express adapters on PCHID 100 and 12C are shared between LPARs 08
and 12.

D.2.8 Software exploitation of SMC-R

SMC-R can be implemented on the RoCE and can communicate memory to memory, thus
avoiding the CPU resources of TCP/IP by reducing network latency and improving wall clock
time. It focuses on "time to value" and widespread performance benefits for all TCP
socket-based middleware.
484
IBM z13s Technical Guide
Logical Partitions
Operating Systems dynamically learn PNet ID (I/O configuration)
PR/SM
then group adapters together based on matching PNet IDs
PNet A PNet B
OSA
OSA
RoCE
Switch B Switch A
Network B
CPC
Guest Virtual Machines
z/VM
PNet C
RoCE RoCE
OSA
Switch B Switch A Switch B
Network C
PNet IDs in HCD
IODF HCD
PCHID
PNet ID