Agent skill · nvidia
nvshmem-configure-nic-pe-mapping
Recommend NVSHMEM NIC-to-PE mappings and environment exports. Use for HCA selection, multi-NIC configuration, or topology-based mapping diagnostics.
What it needs
About 9k tokens when loaded.
What this skill does
Tune NVSHMEM NIC-to-PE Mapping Purpose Produce a reproducible recommendation from the target node's actual GPU/NIC topology. Do not promise a performance improvement; present the mapping as a topology-informed starting point that must be validated. Requirements Use an allocated target compute node with visible GPUs and RDMA devices; do not use login-node topology as evidence. Make nvidia-smi and /sys/class/infiniband readable on that node. If /sys is unavailable, make ibvdevinfo available or provide equivalent per-port evidence. Provide the NVSHMEM installation prefix, make nvshmem-info available on the target node, or supply the installed NVSHMEM version explicitly. Use the bundled read-only collector when possible. It requires no API keys, credentials, package installation, or writable filesystem access. Inputs Resolve every required input before emitting exact exports. If values from different sources conflict, identify the conflict and request clarification rather than selecting a value silently. Required inputs NVSHMEM version: Prefer the user-confirmed installed version; otherwise use the collector's [nvshmem-version] output, then nvshmem-info -n on the target node. Retain the complete reported version after normalizing a leading v. Remote transport: Prefer the explicitly selected transport for the target run; otherwise use the target node's NVSHMEM initialization log. Do not infer a transport from topology; request a log when automatic selection is ambiguous. Local PE count: Prefer observed per-rank logs, then launcher configuration, then an explicit user-provided count. Confirm that all evidence describes the same node allocation. Ordered local PE -> GPU index or PCI BDF binding: Prefer observed per-rank binding logs, then launcher binding configuration, then an explicit user mapping. Use CUDAVISIBLEDEVICES only when its rank order is explicitly established. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills nvidia/nvshmem-configure-nic-pe-mapping