utils/manpages: talk about numa[hbm]:X instead of hbm:X directly

hbm:X locations are still supported but the new numa[hbm]:X should be preferred.

Signed-off-by: Brice Goglin <[email protected]>

Author: bgoglin

utils/hwloc/hwloc-bind.1in

@@ -88,7 +88,7 @@ in account when looking for NUMA nodes in the input locations.
 
 This option must be combined with NUMA node locations,
 such as \fI--hbm numa:1\fR for binding on the second HBM node.
-It may also be written as \fIhbm:1\fR.
+It may also be written as \fInuma[hbm]:1\fR.
 .TP
 \fB\-\-no\-hbm\fR
 Ignore high bandwidth memory nodes (Intel Xeon Phi MCDRAM)
@@ -297,7 +297,7 @@ To bind on the memory node local to a PU with largest capacity:
 
 To bind memory on the first high-bandwidth memory node on Intel Xeon Phi:
 
-    $ hwloc-bind --membind hbm:0 -- echo hello
+    $ hwloc-bind --membind numa[mcdram]:0 -- echo hello
     $ hwloc-bind --hbm --membind numa:0 -- echo hello
 
 Note that binding the "echo" command to multiple processors is

utils/hwloc/hwloc.7in

@@ -211,7 +211,7 @@ A set of processors and memory.
 A NUMA node; a set of processors around memory which the processors
 can directly access.
 .
-If \fBhbm\fR is used instead of \fBnumanode\fR in locations,
+If \fBnuma[hbm]\fR is used instead of \fBnumanode\fR in locations,
 command-line tools only consider high-bandwidth memory nodes such as Intel Xeon Phi MCDRAM.
 .
 .TP