+#: build/C/man2/prctl.2:424
+#, no-wrap
+msgid "B<PR_GET_TID_ADDRESS> (since Linux 3.5)"
+msgstr ""
+
+#. commit 300f786b2683f8bb1ec0afb6e1851183a479c86d
+#. type: Plain text
+#: build/C/man2/prctl.2:439
+msgid ""
+"Retrieve the I<clear_child_tid> address set by B<set_tid_address>(2) and "
+"the B<clone>(2) B<CLONE_CHILD_CLEARTID> flag, in the location pointed to by "
+"I<(int\\ **)\\ arg2>. This feature is available only if the kernel is built "
+"with the B<CONFIG_CHECKPOINT_RESTORE> option enabled."
+msgstr ""
+
+#. type: TP
+#: build/C/man2/prctl.2:439
+#, no-wrap
+msgid "B<PR_SET_TIMERSLACK> (since Linux 2.6.28)"
+msgstr ""
+
+#. See https://lwn.net/Articles/369549/
+#. commit 6976675d94042fbd446231d1bd8b7de71a980ada
+#. It seems that it's not possible to set the timer slack to zero;
+#. The minimum value is 1? Seems a little strange.
+#. type: Plain text
+#: build/C/man2/prctl.2:458
+msgid ""
+"Set the current timer slack for the calling thread to the nanosecond value "
+"supplied in I<arg2>. If I<arg2> is less than or equal to zero, reset the "
+"current timer slack to the thread's default timer slack value. The timer "
+"slack is used by the kernel to group timer expirations for the calling "
+"thread that are close to one another; as a consequence, timer expirations "
+"for the thread may be up to the specified number of nanoseconds late (but "
+"will never expire early). Grouping timer expirations can help reduce system "
+"power consumption by minimizing CPU wake-ups."
+msgstr ""
+
+#. List obtained by grepping for futex usage in glibc source
+#. type: Plain text
+#: build/C/man2/prctl.2:478
+msgid ""
+"The timer expirations affected by timer slack are those set by B<select>(2), "
+"B<pselect>(2), B<poll>(2), B<ppoll>(2), B<epoll_wait>(2), B<epoll_pwait>(2), "
+"B<clock_nanosleep>(2), B<nanosleep>(2), and B<futex>(2) (and thus the "
+"library functions implemented via futexes, including "
+"B<pthread_cond_timedwait>(3), B<pthread_mutex_timedlock>(3), "
+"B<pthread_rwlock_timedrdlock>(3), B<pthread_rwlock_timedwrlock>(3), and "
+"B<sem_timedwait>(3))."
+msgstr ""
+
+#. type: Plain text
+#: build/C/man2/prctl.2:482
+msgid ""
+"Timer slack is not applied to threads that are scheduled under a realtime "
+"scheduling policy (see B<sched_setscheduler>(2))."
+msgstr ""
+
+#. type: Plain text
+#: build/C/man2/prctl.2:499
+msgid ""
+"Each thread has two associated timer slack values: a \"default\" value, and "
+"a \"current\" value. The current value is the one that governs grouping of "
+"timer expirations. When a new thread is created, the two timer slack values "
+"are made the same as the current value of the creating thread. Thereafter, "
+"a thread can adjust its current timer slack value via B<PR_SET_TIMERSLACK> "
+"(the default value can't be changed). The timer slack values of I<init> "
+"(PID 1), the ancestor of all processes, are 50,000 nanoseconds (50 "
+"microseconds). The timer slack values are preserved across B<execve>(2)."
+msgstr ""
+
+#. type: TP
+#: build/C/man2/prctl.2:499
+#, no-wrap
+msgid "B<PR_GET_TIMERSLACK> (since Linux 2.6.28)"
+msgstr ""
+
+#. type: Plain text
+#: build/C/man2/prctl.2:502
+msgid "Return the current timer slack value of the calling thread."
+msgstr ""
+
+#. type: TP
+#: build/C/man2/prctl.2:502