aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorMichael Kerrisk <mtk.manpages@gmail.com>2014-01-21 03:40:40 +0100
committerMichael Kerrisk <mtk.manpages@gmail.com>2014-01-24 11:44:56 +0100
commit31c1f2b09ead1bcd800b6aa40f33b6dce9280b05 (patch)
tree5680f8d7bc0ee2f06530b2b90461b58d0b3da8b4
parentbbe02b45fbe41c3c25561bc69ca98064d27af3e5 (diff)
downloadman-pages-31c1f2b09ead1bcd800b6aa40f33b6dce9280b05.tar.gz
getrlimit.2, madvise.2, mount.2, open.2, perf_event_open.2, send.2: tfix: Consistent capitalization for "(since Linux...)"
Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
Diffstat
-rw-r--r--man2/getrlimit.28
-rw-r--r--man2/madvise.210
-rw-r--r--man2/mount.24
-rw-r--r--man2/open.28
-rw-r--r--man2/perf_event_open.296
-rw-r--r--man2/send.24
6 files changed, 65 insertions, 65 deletions
diff --git a/man2/getrlimit.2 b/man2/getrlimit.2
index f608b928ba..3ab1be4156 100644
--- a/man2/getrlimit.2
+++ b/man2/getrlimit.2
@@ -240,7 +240,7 @@ Since Linux 2.6.9, no limits are placed on the amount of memory
that a privileged process may lock, and this limit instead governs
the amount of memory that an unprivileged process may lock.
.TP
-.BR RLIMIT_MSGQUEUE " (Since Linux 2.6.8)"
+.BR RLIMIT_MSGQUEUE " (since Linux 2.6.8)"
Specifies the limit on the number of bytes that can be allocated
for POSIX message queues for the real user ID of the calling process.
This limit is enforced for
@@ -313,14 +313,14 @@ specifying
.\" talk of making it do something has surfaced from time to time in LKML
.\" -- MTK, Jul 05
.TP
-.BR RLIMIT_RTPRIO " (Since Linux 2.6.12, but see BUGS)"
+.BR RLIMIT_RTPRIO " (since Linux 2.6.12, but see BUGS)"
Specifies a ceiling on the real-time priority that may be set for
this process using
.BR sched_setscheduler (2)
and
.BR sched_setparam (2).
.TP
-.BR RLIMIT_RTTIME " (Since Linux 2.6.25)"
+.BR RLIMIT_RTTIME " (since Linux 2.6.25)"
Specifies a limit (in microseconds)
on the amount of CPU time that a process scheduled
under a real-time scheduling policy may consume without making a blocking
@@ -346,7 +346,7 @@ signal.
The intended use of this limit is to stop a runaway
real-time process from locking up the system.
.TP
-.BR RLIMIT_SIGPENDING " (Since Linux 2.6.8)"
+.BR RLIMIT_SIGPENDING " (since Linux 2.6.8)"
Specifies the limit on the number of signals
that may be queued for the real user ID of the calling process.
Both standard and real-time signals are counted for the purpose of
diff --git a/man2/madvise.2 b/man2/madvise.2
index c2ba0be724..84e017b371 100644
--- a/man2/madvise.2
+++ b/man2/madvise.2
@@ -98,7 +98,7 @@ either in reloading of the memory contents from the underlying mapped file
or zero-fill-on-demand pages for mappings
without an underlying file.
.TP
-.BR MADV_REMOVE " (Since Linux 2.6.16)"
+.BR MADV_REMOVE " (since Linux 2.6.16)"
Free up a given range of pages
and its associated backing store.
Currently,
@@ -111,7 +111,7 @@ error
.\" disk/swap space. This feature is also useful for supporting
.\" hot-plug memory on UML.
.TP
-.BR MADV_DONTFORK " (Since Linux 2.6.16)"
+.BR MADV_DONTFORK " (since Linux 2.6.16)"
.\" See http://lwn.net/Articles/171941/
Do not make the pages in this range available to the child after a
.BR fork (2).
@@ -142,13 +142,13 @@ DMAs into the page(s).)
.\" SEE ALSO: http://lwn.net/Articles/171941/
.\" "Tweaks to madvise() and posix_fadvise()", 14 Feb 2006
.TP
-.BR MADV_DOFORK " (Since Linux 2.6.16)"
+.BR MADV_DOFORK " (since Linux 2.6.16)"
Undo the effect of
.BR MADV_DONTFORK ,
restoring the default behavior, whereby a mapping is inherited across
.BR fork (2).
.TP
-.BR MADV_HWPOISON " (Since Linux 2.6.32)
+.BR MADV_HWPOISON " (since Linux 2.6.32)
Poison a page and handle it like a hardware memory corruption.
This operation is available only for privileged
.RB ( CAP_SYS_ADMIN )
@@ -160,7 +160,7 @@ This feature is intended for testing of memory error-handling code;
it is available only if the kernel was configured with
.BR CONFIG_MEMORY_FAILURE .
.TP
-.BR MADV_SOFT_OFFLINE " (Since Linux 2.6.33)
+.BR MADV_SOFT_OFFLINE " (since Linux 2.6.33)
Soft offline the pages in the range specified by
.I addr
and
diff --git a/man2/mount.2 b/man2/mount.2
index 23b52dc2fc..68403ac5b2 100644
--- a/man2/mount.2
+++ b/man2/mount.2
@@ -206,7 +206,7 @@ Mount filesystem read-only.
.\" This flag has meaning in conjunction with MS_BIND and
.\" also with the shared subtree flags.
.TP
-.BR MS_RELATIME " (Since Linux 2.6.20)"
+.BR MS_RELATIME " (since Linux 2.6.20)"
When a file on this filesystem is accessed,
update the file's last access time (atime) only if the current value
of atime is less than or equal to the file's last modification time (mtime)
@@ -266,7 +266,7 @@ This flag supersedes the misnamed and obsolete
.BR MS_VERBOSE
flag (available since Linux 2.4.12), which has the same meaning.
.TP
-.BR MS_STRICTATIME " (Since Linux 2.6.30)"
+.BR MS_STRICTATIME " (since Linux 2.6.30)"
Always update the last access time (atime) when files on this
filesystem are accessed.
(This was the default behavior before Linux 2.6.30.)
diff --git a/man2/open.2 b/man2/open.2
index ccb1d260b2..1b5e7bd431 100644
--- a/man2/open.2
+++ b/man2/open.2
@@ -181,7 +181,7 @@ See
.BR fcntl (2)
for further details.
.TP
-.BR O_CLOEXEC " (Since Linux 2.6.23)"
+.BR O_CLOEXEC " (since Linux 2.6.23)"
Enable the close-on-exec flag for the new file descriptor.
Specifying this flag permits a program to avoid additional
.BR fcntl (2)
@@ -289,7 +289,7 @@ The following symbolic constants are provided for
00001 others have execute permission
.RE
.TP
-.BR O_TMPFILE " (Since Linux 3.11)"
+.BR O_TMPFILE " (since Linux 3.11)"
.\" commit 60545d0d4610b02e55f65d141c95b18ccf855b6e
.\" commit f4e0c30c191f87851c4a53454abb55ee276f4a7e
.\" commit bb458c644a59dbba3a1fe59b27106c5e68e1c4bd
@@ -364,7 +364,7 @@ requires support by the underlying filesystem;
.\" As at 3.13, there's support for at least ext2, ext3, ext4
only a subset of Linux filesystems provide that support.
.TP
-.BR O_DIRECT " (Since Linux 2.4.10)"
+.BR O_DIRECT " (since Linux 2.4.10)"
Try to minimize cache effects of the I/O to and from this file.
In general this will degrade performance, but it is useful in
special situations, such as when applications do their own caching.
@@ -475,7 +475,7 @@ is the preferred
method of accessing large files on 32-bit systems (see
.BR feature_test_macros (7)).
.TP
-.BR O_NOATIME " (Since Linux 2.6.8)"
+.BR O_NOATIME " (since Linux 2.6.8)"
Do not update the file last access time
.RI ( st_atime
in the inode)
diff --git a/man2/perf_event_open.2 b/man2/perf_event_open.2
index 377b1d6d12..8cff4c8f0d 100644
--- a/man2/perf_event_open.2
+++ b/man2/perf_event_open.2
@@ -142,7 +142,7 @@ It is unclear why this is useful.
.BR PERF_FLAG_FD_OUTPUT
This flag reroutes the output from an event to the group leader.
.TP
-.BR PERF_FLAG_PID_CGROUP " (Since Linux 2.6.39)."
+.BR PERF_FLAG_PID_CGROUP " (since Linux 2.6.39)."
This flag activates per-container system-wide monitoring.
A container
is an abstraction that isolates a set of resources for finer grain
@@ -271,7 +271,7 @@ field definition.
This indicates a "raw" implementation-specific event in the
.IR config " field."
.TP
-.BR PERF_TYPE_BREAKPOINT " (Since Linux 2.6.33)"
+.BR PERF_TYPE_BREAKPOINT " (since Linux 2.6.33)"
This indicates a hardware breakpoint as provided by the CPU.
Breakpoints can be read/write accesses to an address as well as
execution of an instruction address.
@@ -393,13 +393,13 @@ Mispredicted branch instructions.
.B PERF_COUNT_HW_BUS_CYCLES
Bus cycles, which can be different from total cycles.
.TP
-.BR PERF_COUNT_HW_STALLED_CYCLES_FRONTEND " (Since Linux 3.0)"
+.BR PERF_COUNT_HW_STALLED_CYCLES_FRONTEND " (since Linux 3.0)"
Stalled cycles during issue.
.TP
-.BR PERF_COUNT_HW_STALLED_CYCLES_BACKEND " (Since Linux 3.0)"
+.BR PERF_COUNT_HW_STALLED_CYCLES_BACKEND " (since Linux 3.0)"
Stalled cycles during retirement.
.TP
-.BR PERF_COUNT_HW_REF_CPU_CYCLES " (Since Linux 3.3)"
+.BR PERF_COUNT_HW_REF_CPU_CYCLES " (since Linux 3.3)"
Total cycles; not affected by CPU frequency scaling.
.RE
.IP
@@ -439,19 +439,19 @@ These did not require disk I/O to handle.
This counts the number of major page faults.
These required disk I/O to handle.
.TP
-.BR PERF_COUNT_SW_ALIGNMENT_FAULTS " (Since Linux 2.6.33)"
+.BR PERF_COUNT_SW_ALIGNMENT_FAULTS " (since Linux 2.6.33)"
This counts the number of alignment faults.
These happen when unaligned memory accesses happen; the kernel
can handle these but it reduces performance.
This happens only on some architectures (never on x86).
.TP
-.BR PERF_COUNT_SW_EMULATION_FAULTS " (Since Linux 2.6.33)"
+.BR PERF_COUNT_SW_EMULATION_FAULTS " (since Linux 2.6.33)"
This counts the number of emulation faults.
The kernel sometimes traps on unimplemented instructions
and emulates them for user space.
This can negatively impact performance.
.TP
-.BR PERF_COUNT_SW_DUMMY " (Since Linux 3.12)"
+.BR PERF_COUNT_SW_DUMMY " (since Linux 3.12)"
This is a placeholder event that counts nothing.
Informational sample record types such as mmap or comm
must be associated with an active event.
@@ -511,7 +511,7 @@ for measuring the Instruction TLB
.B PERF_COUNT_HW_CACHE_BPU
for measuring the branch prediction unit
.TP
-.BR PERF_COUNT_HW_CACHE_NODE " (Since Linux 3.0)"
+.BR PERF_COUNT_HW_CACHE_NODE " (since Linux 3.0)"
for measuring local memory accesses
.RE
.P
@@ -643,7 +643,7 @@ This ID is the same as the one returned by
Records additional data, if applicable.
Usually returned by tracepoint events.
.TP
-.BR PERF_SAMPLE_BRANCH_STACK " (Since Linux 3.4)"
+.BR PERF_SAMPLE_BRANCH_STACK " (since Linux 3.4)"
This provides a record of recent branches, as provided
by CPU branch sampling hardware (such as Intel Last Branch Record).
Not all hardware supports this feature.
@@ -652,26 +652,26 @@ See the
.I branch_sample_type
field for how to filter which branches are reported.
.TP
-.BR PERF_SAMPLE_REGS_USER " (Since Linux 3.7)"
+.BR PERF_SAMPLE_REGS_USER " (since Linux 3.7)"
Records the current user-level CPU register state
(the values in the process before the kernel was called).
.TP
-.BR PERF_SAMPLE_STACK_USER " (Since Linux 3.7)"
+.BR PERF_SAMPLE_STACK_USER " (since Linux 3.7)"
Records the user level stack, allowing stack unwinding.
.TP
-.BR PERF_SAMPLE_WEIGHT " (Since Linux 3.10)"
+.BR PERF_SAMPLE_WEIGHT " (since Linux 3.10)"
Records a hardware provided weight value that expresses how
costly the sampled event was.
This allows the hardware to highlight expensive events in
a profile.
.TP
-.BR PERF_SAMPLE_DATA_SRC " (Since Linux 3.10)"
+.BR PERF_SAMPLE_DATA_SRC " (since Linux 3.10)"
Records the data source: where in the memory hierarchy
the data associated with the sampled instruction came from.
This is only available if the underlying hardware
supports this feature.
.TP
-.BR PERF_SAMPLE_IDENTIFIER " (Since Linux 3.12)"
+.BR PERF_SAMPLE_IDENTIFIER " (since Linux 3.12)"
Places the
.B SAMPLE_ID
value in a fixed position in the record,
@@ -879,7 +879,7 @@ Otherwise interrupts happen after
.I wakeup_events
samples.
.TP
-.IR "precise_ip" " (Since Linux 2.6.35)"
+.IR "precise_ip" " (since Linux 2.6.35)"
This controls the amount of skid.
Skid is how many instructions
execute between an event of interest happening and the kernel
@@ -911,7 +911,7 @@ See also
.BR PERF_RECORD_MISC_EXACT_IP .
.RE
.TP
-.IR "mmap_data" " (Since Linux 2.6.36)"
+.IR "mmap_data" " (since Linux 2.6.36)"
The counterpart of the
.I mmap
field.
@@ -923,7 +923,7 @@ calls that do not have
.B PROT_EXEC
set (for example data and SysV shared memory).
.TP
-.IR "sample_id_all" " (Since Linux 2.6.38)"
+.IR "sample_id_all" " (since Linux 2.6.38)"
If set, then TID, TIME, ID, STREAM_ID, and CPU can
additionally be included in
.RB non- PERF_RECORD_SAMPLE s
@@ -952,16 +952,16 @@ struct sample_id {
};
.fi
.TP
-.IR "exclude_host" " (Since Linux 3.2)"
+.IR "exclude_host" " (since Linux 3.2)"
Do not measure time spent in VM host.
.TP
-.IR "exclude_guest" " (Since Linux 3.2)"
+.IR "exclude_guest" " (since Linux 3.2)"
Do not measure time spent in VM guest.
.TP
-.IR "exclude_callchain_kernel" " (Since Linux 3.7)"
+.IR "exclude_callchain_kernel" " (since Linux 3.7)"
Do not include kernel callchains.
.TP
-.IR "exclude_callchain_user" " (Since Linux 3.7)"
+.IR "exclude_callchain_user" " (since Linux 3.7)"
Do not include user callchains.
.TP
.IR "wakeup_events" ", " "wakeup_watermark"
@@ -984,7 +984,7 @@ type set
.I wakeup_watermark
to 1.
.TP
-.IR "bp_type" " (Since Linux 2.6.33)"
+.IR "bp_type" " (since Linux 2.6.33)"
This chooses the breakpoint type.
It is one of:
.RS
@@ -1014,21 +1014,21 @@ with
is not allowed.
.RE
.TP
-.IR "bp_addr" " (Since Linux 2.6.33)"
+.IR "bp_addr" " (since Linux 2.6.33)"
.I bp_addr
address of the breakpoint.
For execution breakpoints this is the memory address of the instruction
of interest; for read and write breakpoints it is the memory address
of the memory location of interest.
.TP
-.IR "config1" " (Since Linux 2.6.39)"
+.IR "config1" " (since Linux 2.6.39)"
.I config1
is used for setting events that need an extra register or otherwise
do not fit in the regular config field.
Raw OFFCORE_EVENTS on Nehalem/Westmere/SandyBridge use this field
on 3.3 and later kernels.
.TP
-.IR "bp_len" " (Since Linux 2.6.33)"
+.IR "bp_len" " (since Linux 2.6.33)"
.I bp_len
is the length of the breakpoint being measured if
.I type
@@ -1042,14 +1042,14 @@ Options are
For an execution breakpoint, set this to
.IR sizeof(long) .
.TP
-.IR "config2" " (Since Linux 2.6.39)"
+.IR "config2" " (since Linux 2.6.39)"
.I config2
is a further extension of the
.I config1
field.
.TP
-.IR "branch_sample_type" " (Since Linux 3.4)"
+.IR "branch_sample_type" " (since Linux 3.4)"
If
.B PERF_SAMPLE_BRANCH_STACK
is enabled, then this specifies what branches to include
@@ -1091,24 +1091,24 @@ Any return branch.
.B PERF_SAMPLE_BRANCH_IND_CALL
Indirect calls.
.TP
-.BR PERF_SAMPLE_BRANCH_ABORT_TX " (Since Linux 3.11)"
+.BR PERF_SAMPLE_BRANCH_ABORT_TX " (since Linux 3.11)"
Transactional memory aborts.
.TP
-.BR PERF_SAMPLE_BRANCH_IN_TX " (Since Linux 3.11)"
+.BR PERF_SAMPLE_BRANCH_IN_TX " (since Linux 3.11)"
Branch in transactional memory transaction.
.TP
-.BR PERF_SAMPLE_BRANCH_NO_TX " (Since Linux 3.11)"
+.BR PERF_SAMPLE_BRANCH_NO_TX " (since Linux 3.11)"
Branch not in transactional memory transaction.
.RE
.TP
-.IR "sample_regs_user" " (Since Linux 3.7)"
+.IR "sample_regs_user" " (since Linux 3.7)"
This bit mask defines the set of user CPU registers to dump on samples.
The layout of the register mask is architecture-specific and
described in the kernel header
.IR arch/ARCH/include/uapi/asm/perf_regs.h .
.TP
-.IR "sample_stack_user" " (Since Linux 3.7)"
+.IR "sample_stack_user" " (since Linux 3.7)"
This defines the size of the user stack to dump if
.B PERF_SAMPLE_STACK_USER
is specified.
@@ -1273,7 +1273,7 @@ Time the event was active.
.I time_running
Time the event was running.
.TP
-.IR cap_usr_time " / " cap_usr_rdpmc " / " cap_bit0 " (Since Linux 3.4)"
+.IR cap_usr_time " / " cap_usr_rdpmc " / " cap_bit0 " (since Linux 3.4)"
There was a bug in the definition of
.I cap_usr_time
and
@@ -1295,7 +1295,7 @@ and
fields instead.
.TP
-.IR cap_bit0_is_deprecated " (Since Linux 3.12)"
+.IR cap_bit0_is_deprecated " (since Linux 3.12)"
If set this bit indicates that the kernel supports
the properly separated
.I cap_user_time
@@ -1311,7 +1311,7 @@ map to the same bit and thus both features should
be used with caution.
.TP
-.IR cap_user_rdpmc " (Since Linux 3.12)"
+.IR cap_user_rdpmc " (since Linux 3.12)"
If the hardware supports user-space read of performance counters
without syscall (this is the "rdpmc" instruction on x86), then
the following code can be used to do a read:
@@ -1348,11 +1348,11 @@ do {
.fi
.in
.TP
-.I cap_user_time " (Since Linux 3.12)"
+.I cap_user_time " (since Linux 3.12)"
This bit indicates the hardware has a constant, nonstop
timestamp counter (TSC on x86).
.TP
-.IR cap_user_time_zero " (Since Linux 3.12)"
+.IR cap_user_time_zero " (since Linux 3.12)"
Indicates the presence of
.I time_zero
which allows mapping timestamp values to
@@ -1409,7 +1409,7 @@ enabled and possible running (if idx), improving the scaling:
count = quot * enabled + (rem * enabled) / running;
.fi
.TP
-.IR time_zero " (Since Linux 3.12)"
+.IR time_zero " (since Linux 3.12)"
If
.I cap_usr_time_zero
@@ -1817,10 +1817,10 @@ The branch target was mispredicted.
.I predicted
The branch target was predicted.
.TP
-.IR in_tx " (Since Linux 3.11)"
+.IR in_tx " (since Linux 3.11)"
The branch was in a transactional memory transaction.
.TP
-.IR abort " (Since Linux 3.11)"
+.IR abort " (since Linux 3.11)"
The branch was in an aborted transactional memory transaction.
.P
@@ -2211,12 +2211,12 @@ The file descriptors must all be on the same CPU.
The argument specifies the desired file descriptor, or \-1 if
output should be ignored.
.TP
-.BR PERF_EVENT_IOC_SET_FILTER " (Since Linux 2.6.33)"
+.BR PERF_EVENT_IOC_SET_FILTER " (since Linux 2.6.33)"
This adds an ftrace filter to this event.
The argument is a pointer to the desired ftrace filter.
.TP
-.BR PERF_EVENT_IOC_ID " (Since Linux 3.12)"
+.BR PERF_EVENT_IOC_ID " (since Linux 3.12)"
Returns the event ID value for the given event fd.
The argument is a pointer to a 64-bit unsigned integer
@@ -2284,17 +2284,17 @@ Information on how to program these PMUs can be found under
.IR /sys/bus/event_source/devices/ .
Each subdirectory corresponds to a different PMU.
.TP
-.IR /sys/bus/event_source/devices/*/type " (Since Linux 2.6.38)"
+.IR /sys/bus/event_source/devices/*/type " (since Linux 2.6.38)"
This contains an integer that can be used in the
.I type
field of perf_event_attr to indicate you wish to use this PMU.
.TP
-.IR /sys/bus/event_source/devices/*/rdpmc " (Since Linux 3.4)"
+.IR /sys/bus/event_source/devices/*/rdpmc " (since Linux 3.4)"
If this file is 1, then direct user-space access to the
performance counter registers is allowed via the rdpmc instruction.
This can be disabled by echoing 0 to the file.
.TP
-.IR /sys/bus/event_source/devices/*/format/ " (Since Linux 3.4)"
+.IR /sys/bus/event_source/devices/*/format/ " (since Linux 3.4)"
This subdirectory contains information on the architecture-specific
subfields available for programming the various
.I config
@@ -2310,7 +2310,7 @@ may contain the value
which indicates that event is an attribute that occupies bits 1,6-10, and 44
of perf_event_attr::config1.
.TP
-.IR /sys/bus/event_source/devices/*/events/ " (Since Linux 3.4)"
+.IR /sys/bus/event_source/devices/*/events/ " (since Linux 3.4)"
This subdirectory contains files with predefined events.
The contents are strings describing the event settings
expressed in terms of the fields found in the previously mentioned
@@ -2331,7 +2331,7 @@ An example entry may look like this:
This file is the standard kernel device interface
for injecting hotplug events.
.TP
-.IR /sys/bus/event_source/devices/*/cpumask " (Since Linux 3.7)"
+.IR /sys/bus/event_source/devices/*/cpumask " (since Linux 3.7)"
The
.I cpumask
file contains a comma-separated list of integers that
diff --git a/man2/send.2 b/man2/send.2
index a6dccc602c..17ec6f01e3 100644
--- a/man2/send.2
+++ b/man2/send.2
@@ -164,7 +164,7 @@ argument is the bitwise OR
of zero or more of the following flags.
.\" FIXME ? document MSG_PROXY (which went away in 2.3.15)
.TP
-.BR MSG_CONFIRM " (Since Linux 2.3.15)"
+.BR MSG_CONFIRM " (since Linux 2.3.15)"
Tell the link layer that forward progress happened: you got a successful
reply from the other side.
If the link layer doesn't get this
@@ -201,7 +201,7 @@ flag with the
Terminates a record (when this notion is supported, as for sockets of type
.BR SOCK_SEQPACKET ).
.TP
-.BR MSG_MORE " (Since Linux 2.4.4)"
+.BR MSG_MORE " (since Linux 2.4.4)"
The caller has more data to send.
This flag is used with TCP sockets to obtain the same effect
as the
generated by cgit 1.2.3-korg (git 2.43.0) at 2025-12-02 01:28:59 +0000