Collecting Information on selected GPFS Nodes

If you wish to collect information from selected nodes from nsdnodes, quoumnodes, mangernodes

# /usr/lpp/mmfs/bin/gpfs.snap -N nsdnodes,quorumnodes,managernodes

Developing a Linux Kernel Module using GPUDirect RDMA

Taken from Developing a Linux Kernel Module using GPUDirect RDMA

1.0 Overview

GPUDirect RDMA is a technology introduced in Kepler-class GPUs and CUDA 5.0 that enables a direct path for data exchange between the GPU and a third-party peer device using standard features of PCI Express. Examples of third-party devices are: network interfaces, video acquisition devices, storage adapters.

GPUDirect RDMA is available on both Tesla and Quadro GPUs.

A number of limitations can apply, the most important being that the two devices must share the same upstream PCI Express root complex. Some of the limitations depend on the platform used and could be lifted in current/future products.

A few straightforward changes must be made to device drivers to enable this functionality with a wide range of hardware devices. This document introduces the technology and describes the steps necessary to enable an GPUDirect RDMA connection to NVIDIA GPUs on Linux.


1.1. How GPUDirect RDMA Works

When setting up GPUDirect RDMA communication between two peers, all physical addresses are the same from the PCI Express devices’ point of view. Within this physical address space are linear windows called PCI BARs. Each device has six BAR registers at most, so it can have up to six active 32bit BAR regions. 64bit BARs consume two BAR registers. The PCI Express device issues reads and writes to a peer device’s BAR addresses in the same way that they are issued to system memory.

Traditionally, resources like BAR windows are mapped to user or kernel address space using the CPU’s MMU as memory mapped I/O (MMIO) addresses. However, because current operating systems don’t have sufficient mechanisms for exchanging MMIO regions between drivers, the NVIDIA kernel driver exports functions to perform the necessary address translations and mappings.

To add GPUDirect RDMA support to a device driver, a small amount of address mapping code within the kernel driver must be modified. This code typically resides near existing calls to get_user_pages().

The APIs and control flow involved with GPUDirect RDMA are very similar to those used with standard DMA transfers.


Read more at:

Remove Mapping of Null User to Windows User or Group in NetAPP

If you need to remove the mapping of null users to windows user or group in NetApp, it can be done with the following steps

Step 1: Set the privilege level to advanced:

# set -privilege advanced

Step 2: Configure the restrict anonymous setting:

# vserver cifs options modify -vserver vserver_name -restrict-anonymous {no-restriction|no-enumeration|no-access}

Step 3: Verify that the option is set to the desired value:

vserver cifs options show -vserver vserver_name

Step 4: Return to the admin privilege level:

set -privilege admin

Compiling Wannier90-2.1.0 with Intel-MPI 5.1.3

Compiling Wannier90-2.1.0 is quite straight-forward.

Step 1: Download the source code from Wannier.Org at

Step 2: Untar the tar-ball

$ tar -zxvf wannier90-2.1.0.tar.gz

Step 3: Copy and Edit the make file

$ cd wannier90-2.1.0/config
$ cp ..
$ cd ..
$ mv
# For Linux with intel version 11/12 on 64bit machines
F90 = ifort
# Intel mkl libraries. Set LIBPATH if not in default path
LIBDIR = /usr/local/RH6_apps/intel/mkl/lib/intel64
LIBS = -L$(LIBDIR) -lmkl_core -lmkl_intel_lp64 -lmkl_sequential -lpthread
#LIBDIR = /usr/local/lib
#LIBS = -L$(LIBDIR) -llapack -lf77blas -lcblas -latlas
$ make default -j 8
$ make lib
$ make w90chk2chk
$ make w90vdw
$ make w90pov
$ make test
$ make doc

IF you need to restart the compilation, you use the command

$ make veryclean

For more information, do take a look at