add_key.2, alloc_hugepages.2, execve.2, fanotify_init.2, getrlimit.2, listxattr.2, mmap.2, shmget.2, malloc.3, random.4, st.4, bootparam.7, epoll.7, keyrings.7, pipe.7, xattr.7: Use non-breaking space for measurement units

Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>

man2/add_key.2

@@ -133,7 +133,7 @@ contains a ':' that is preceded by other characters.
 .\" commit ab3c3587f8cda9083209a61dbe3a4407d3cada10
 This key type is similar to
 .IR """user""" ,
-but may hold a payload of up to 1 MiB.
+but may hold a payload of up to 1\ MiB.
 If the key payload is large enough,
 then it may be stored encrypted in tmpfs
 (which can be swapped out) rather than kernel memory.

man2/alloc_hugepages.2

@@ -47,8 +47,8 @@ In Linux 2.4.20, the syscall numbers exist,
 but the calls fail with the error
 .BR ENOSYS .
 .PP
-On i386 the memory management hardware knows about ordinary pages (4 KiB)
-and huge pages (2 or 4 MiB).
+On i386 the memory management hardware knows about ordinary pages (4\ KiB)
+and huge pages (2 or 4\ MiB).
 Similarly ia64 knows about huge pages of
 several sizes.
 These system calls serve to map huge pages into the

man2/execve.2

@@ -357,7 +357,7 @@ environment and argument strings was limited to 32 pages
 (defined by the kernel constant
 .BR MAX_ARG_PAGES ).
 On architectures with a 4-kB page size,
-this yields a maximum size of 128 kB.
+this yields a maximum size of 128\ kB.
 .PP
 On kernel 2.6.23 and later, most architectures support a size limit
 derived from the soft

man2/fanotify_init.2

@@ -170,7 +170,7 @@ Additional bits can be set in
 The most useful values are:
 .TP
 .B O_LARGEFILE
-Enable support for files exceeding 2 GB.
+Enable support for files exceeding 2\ GB.
 Failing to set this flag will result in an
 .B EOVERFLOW
 error when trying to open a large file which is monitored by

man2/getrlimit.2

@@ -143,7 +143,7 @@ that kills the process if no alternate stack
 has been made available via
 .BR sigaltstack (2)).
 Since the value is a \fIlong\fP, on machines with a 32-bit \fIlong\fP
-either this limit is at most 2 GiB, or this resource is unlimited.
+either this limit is at most 2\ GiB, or this resource is unlimited.
 .TP
 .B RLIMIT_CORE
 This is the maximum size of a

man2/listxattr.2

@@ -170,7 +170,7 @@ These system calls are Linux-specific.
 .\" The xattr(7) page refers to this text:
 As noted in
 .BR xattr (7),
-the VFS imposes a limit of 64 kB on the size of the extended
+the VFS imposes a limit of 64\ kB on the size of the extended
 attribute name list returned by
 .BR listxattr (7).
 If the total size of attribute names attached to a file exceeds this limit,

man2/mmap.2

@@ -249,7 +249,7 @@ for further information, as well as NOTES, below.
 .\" See https://lwn.net/Articles/533499/
 Used in conjunction with
 .B MAP_HUGETLB
-to select alternative hugetlb page sizes (respectively, 2 MB and 1 GB)
+to select alternative hugetlb page sizes (respectively, 2\ MB and 1\ GB)
 on systems that support multiple hugetlb page sizes.
 .IP
 More generally, the desired huge page size can be configured by encoding

man2/shmget.2

@@ -116,7 +116,7 @@ for further information.
 .\" See https://lwn.net/Articles/533499/
 Used in conjunction with
 .B SHM_HUGETLB
-to select alternative hugetlb page sizes (respectively, 2 MB and 1 GB)
+to select alternative hugetlb page sizes (respectively, 2\ MB and 1\ GB)
 on systems that support multiple hugetlb page sizes.
 .IP
 More generally, the desired huge page size can be configured by encoding
@@ -338,7 +338,7 @@ If
 and
 .B SHMMNI
 were not modified, then multiplying the result of this formula
-by the page size (to get a value in bytes) yielded a value of 8 GB
+by the page size (to get a value in bytes) yielded a value of 8\ GB
 as the limit on the total memory used by all shared memory segments.
 .TP
 .B SHMMAX
@@ -368,7 +368,7 @@ Because it is not possible to map just part of a shared memory segment,
 the amount of virtual memory places another limit on the maximum size of a
 usable segment:
 for example, on i386 the largest segments that can be mapped have a
-size of around 2.8 GB, and on x86_64 the limit is around 127 TB.
+size of around 2.8\ GB, and on x86_64 the limit is around 127 TB.
 .TP
 .B SHMMIN
 Minimum size in bytes for a shared memory segment: implementation

man3/malloc.3

@@ -286,7 +286,7 @@ bytes, the glibc
 implementation allocates the memory as a private anonymous mapping using
 .BR mmap (2).
 .B MMAP_THRESHOLD
-is 128 kB by default, but is adjustable using
+is 128\ kB by default, but is adjustable using
 .BR mallopt (3).
 Allocations performed using
 .BR mmap (2)

man4/random.4

@@ -109,7 +109,7 @@ a
 .BR read (2)
 from
 .IR /dev/urandom
-will return at most 32 MB.
+will return at most 32\ MB.
 A
 .BR read (2)
 from

man4/st.4

@@ -101,14 +101,14 @@ In kernels before 2.1.121, the buffer is
 allocated as one contiguous block.
 This limits the block size to the
 largest contiguous block of memory the kernel allocator can provide.
-The limit is currently 128 kB for 32-bit architectures and
-256 kB for 64-bit architectures.
+The limit is currently 128\ kB for 32-bit architectures and
+256\ kB for 64-bit architectures.
 In newer kernels the driver
 allocates the buffer in several parts if necessary.
 By default, the
 maximum number of parts is 16.
 This means that the maximum block size
-is very large (2 MB if allocation of 16 blocks of 128 kB succeeds).
+is very large (2\ MB if allocation of 16 blocks of 128\ kB succeeds).
 .PP
 The driver's internal buffer size is determined by a compile-time
 constant which can be overridden with a kernel startup option.

man7/bootparam.7

@@ -351,7 +351,7 @@ If N=0, do not prompt.
 .TP
 .BR 'ramdisk_size=N' " or (obsolete) " 'ramdisk=N'
 Set the maximal size of the ramdisk(s) to N kB.
-The default is 4096 (4 MB).
+The default is 4096 (4\ MB).
 .TP
 .B "'ramdisk_start=N'"
 Sets the starting block number (the offset on the floppy where

man7/epoll.7

@@ -74,7 +74,7 @@ is registered on the
 .B epoll
 instance.
 .IP 2.
-A pipe writer writes 2 kB of data on the write side of the pipe.
+A pipe writer writes 2\ kB of data on the write side of the pipe.
 .IP 3.
 A call to
 .BR epoll_wait (2)
@@ -82,7 +82,7 @@ is done that will return
 .I rfd
 as a ready file descriptor.
 .IP 4.
-The pipe reader reads 1 kB of data from
+The pipe reader reads 1\ kB of data from
 .IR rfd .
 .IP 5.
 A call to

man7/keyrings.7

@@ -147,7 +147,7 @@ that should not be readable from user space.
 .\" commit ab3c3587f8cda9083209a61dbe3a4407d3cada10
 This key type is similar to the
 .I """user"""
-key type, but it may hold a payload of up to 1 MiB in size.
+key type, but it may hold a payload of up to 1\ MiB in size.
 This key type is useful for purposes such as holding Kerberos ticket caches.
 .IP
 The payload data may be stored in a tmpfs filesystem,

man7/pipe.7

@@ -190,7 +190,7 @@ to reflect the value actually employed for a convenient implementation.
 To determine the rounded-up value,
 display the contents of this file after assigning a value to it.
 .IP
-The default value for this file is 1048576 (1 MiB).
+The default value for this file is 1048576 (1\ MiB).
 The minimum value that can be assigned to this file is the system page size.
 Attempts to set a limit less than the page size cause
 .BR write (2)

man7/xattr.7

@@ -139,9 +139,9 @@ manual page for an explanation of the sticky bit).
 The kernel and the filesystem may place limits on the maximum number
 and size of extended attributes that can be associated with a file.
 The VFS imposes limitations that an attribute names is limited to 255 bytes
-and an attribute value is limited to 64 kB.
+and an attribute value is limited to 64\ kB.
 The list of attribute names that
-can be returned is also limited to 64 kB
+can be returned is also limited to 64\ kB
 (see BUGS in
 .BR listxattr (2)).
 .PP
@@ -168,7 +168,7 @@ In the Btrfs filesystem implementation,
 the total bytes used for the name, value, and implementation overhead bytes
 is limited to the filesystem
 .I nodesize
-value (16 kB by default).
+value (16\ kB by default).
 .SH CONFORMING TO
 Extended attributes are not specified in POSIX.1, but some other systems
 (e.g., the BSDs and Solaris) provide a similar feature.