From 2cd276f3988f0110eabdbba30cde70dbce47368c Mon Sep 17 00:00:00 2001 From: Michael Kerrisk Date: Thu, 6 Aug 2015 14:00:17 +0200 Subject: [PATCH] __ppc_yield.3: Minor tweaks Signed-off-by: Michael Kerrisk --- man3/__ppc_yield.3 | 24 ++++++------------------ 1 file changed, 6 insertions(+), 18 deletions(-) diff --git a/man3/__ppc_yield.3 b/man3/__ppc_yield.3 index 6a06cc9f12..9f84bbde90 100644 --- a/man3/__ppc_yield.3 +++ b/man3/__ppc_yield.3 @@ -22,9 +22,6 @@ .\" the source, must acknowledge the copyright and authors of this work. .\" %%%LICENSE_END .\" -.\" Process this file with -.\" groff -man -Tascii foo.1 -.\" .TH __PPC_YIELD 3 2015-08-05 "GNU C Library" "Linux Programmer's\ Manual" .SH NAME @@ -39,17 +36,11 @@ Hint the processor to release shared resources .br .B void __ppc_mdoom(void); .SH DESCRIPTION -The functions -.BR __ppc_yield (), -.BR __ppc_mdoio () -and -.BR __ppc_mdoom () +These functions provide hints about the usage of resources that are shared with other -processors. +processors on the Power architecture. They can be used, for example, if a program waiting on a lock intends to divert the shared resources to be used by other processors. -More information is available in Power ISA 2.06b - Book II - Section -3.2. .P .BR __ppc_yield () provides a hint that performance will probably be improved if shared @@ -68,19 +59,14 @@ resources dedicated to the executing processor are released until all outstanding storage accesses to cacheable storage for which the data is not in the cache have been completed. .SH VERSIONS -GNU C Library added support for -.BR __ppc_yield (), -.BR __ppc_mdoio () -and -.BR __ppc_mdoom () -in version 2.18. +These functions first appeared in glibc in version 2.18. .SH ATTRIBUTES For an explanation of the terms used in this section, see .BR attributes (7). .ad l .TS allbox; -lb lb lb +lbw29 lb lb l l l. Interface Attribute Value T{ @@ -94,3 +80,5 @@ T} Thread safety MT-Safe These functions are nonstandard GNU extensions. .SH SEE ALSO .BR __ppc_set_ppr_med (3) + +.IR "Power ISA, Book\ II - Section\ 3.2 (""or"" architecture)" -- 2.47.2