diff --git a/man2/perf_event_open.2 b/man2/perf_event_open.2 index aea239680..8d61cf35a 100644 --- a/man2/perf_event_open.2 +++ b/man2/perf_event_open.2 @@ -789,9 +789,9 @@ disrupt other hardware counters. Note that many unexpected situations may prevent events with the .I exclusive -bit set from ever running. +bit set from ever running. This includes any users running a system-wide -measurement as well as any kernel use of the performance counters +measurement as well as any kernel use of the performance counters (including the commonly enabled NMI Watchdog Timer interface). .TP .IR "exclude_user" diff --git a/man2/reboot.2 b/man2/reboot.2 index 152f3469e..86b2b6d07 100644 --- a/man2/reboot.2 +++ b/man2/reboot.2 @@ -147,7 +147,7 @@ If not preceded by a .BR sync (2), data will be lost. .TP -.BR LINUX_REBOOT_CMD_SW_SUSPEND +.BR LINUX_REBOOT_CMD_SW_SUSPEND .RB ( RB_SW_SUSPEND , 0xd000fce1; since Linux 2.5.18). The system is suspended (hibernated) to disk. diff --git a/man3/string.3 b/man3/string.3 index 0dee9e024..4f7640564 100644 --- a/man3/string.3 +++ b/man3/string.3 @@ -48,13 +48,13 @@ Compare the first .I n characters of the strings .I s1 -and -.I s2 +and +.I s2 ignoring case. .TP .BI "char *index(const char *" s ", int " c ); Return a pointer to the first occurrence of the character -.I c +.I c in the string .IR s . .TP @@ -200,7 +200,7 @@ Transforms .I src to the current locale and copies the first .I n -characters to +characters to .IR dest . .fi .SH DESCRIPTION diff --git a/man5/proc.5 b/man5/proc.5 index e808add5a..2024c7500 100644 --- a/man5/proc.5 +++ b/man5/proc.5 @@ -1876,7 +1876,7 @@ The is calculated using the following formula: CommitLimit = - ([total RAM pages] - [total huge TLB pages]) * + ([total RAM pages] - [total huge TLB pages]) * overcommit_ratio / 100 + [total swap pages] For example, on a system with 1GB of physical RAM and 7GB diff --git a/man7/credentials.7 b/man7/credentials.7 index 19c405bab..1390c11b7 100644 --- a/man7/credentials.7 +++ b/man7/credentials.7 @@ -144,7 +144,7 @@ When terminal keys that generate a signal (such as the key, normally control-C) are pressed, the signal is sent to the processes in the foreground job. -Various system calls and library functions +Various system calls and library functions may operate on all members of a process group, including .BR kill (2), diff --git a/man7/feature_test_macros.7 b/man7/feature_test_macros.7 index bfdc3d37a..468d8bed5 100644 --- a/man7/feature_test_macros.7 +++ b/man7/feature_test_macros.7 @@ -283,7 +283,7 @@ System V-derived definitions. .TP .BR _DEFAULT_SOURCE " (since glibc 2.19)" Defining this macro provides an effect similar to -the feature test macros that are defined by default; that is: +the feature test macros that are defined by default; that is: cc \-D_BSD_SOURCE \-D_SVID_SOURCE \-D_POSIX_C_SOURCE=200809 diff --git a/man7/vdso.7 b/man7/vdso.7 index 180361829..725156187 100644 --- a/man7/vdso.7 +++ b/man7/vdso.7 @@ -32,7 +32,7 @@ There are some system calls the kernel provides that user-space code ends up using frequently, to the point that such calls can dominate overall performance. This is due both to the frequency of the call as well as the -context-switch overhead that results from +context-switch overhead that results from from exiting user space and entering the kernel. The rest of this documentation is geared toward the curious and/or @@ -79,7 +79,7 @@ call and a few memory accesses. .SS Finding the vDSO The base address of the vDSO (if one exists) is passed by the kernel to each program in the initial auxiliary vector (see -.BR getauxval (3)), +.BR getauxval (3)), via the .B AT_SYSINFO_EHDR tag. @@ -136,7 +136,7 @@ You will frequently find it under the architecture-specific directory: .SS vDSO names The name of vDSO shared object varies across architectures. -It will often show up in things like glibc's +It will often show up in things like glibc's .BR ldd (1) output. The exact name should not matter to any code, so do not hardcode it. @@ -488,7 +488,7 @@ __vdso_time LINUX_2.6 The vDSO was originally just a single function\(emthe vsyscall. In older kernels, you might see that name in a process's memory map rather than "vdso". -Over time, people realized that this mechanism +Over time, people realized that this mechanism was a great way to pass more functionality to user space, so it was reconceived as a vDSO in the current format. .SH SEE ALSO