public inbox for linux-man@vger.kernel.org
 help / color / mirror / Atom feed
From: Alejandro Colomar <alx.manpages@gmail.com>
To: linux-man@vger.kernel.org, a.clayton@nginx.com
Cc: Alejandro Colomar <alx@kernel.org>, andrew@digital-domain.net
Subject: [PATCH 1/3] sched_yield.2: HISTORY: POSIX.1-2008 makes this non-optional
Date: Wed,  3 May 2023 19:03:51 +0200	[thread overview]
Message-ID: <20230503170353.25998-2-alx@kernel.org> (raw)
In-Reply-To: <20230503170353.25998-1-alx@kernel.org>

Signed-off-by: Alejandro Colomar <alx@kernel.org>
---
 man2/sched_yield.2 | 18 ++++++++++--------
 1 file changed, 10 insertions(+), 8 deletions(-)

diff --git a/man2/sched_yield.2 b/man2/sched_yield.2
index f1024762a..bab0f9569 100644
--- a/man2/sched_yield.2
+++ b/man2/sched_yield.2
@@ -38,20 +38,22 @@ .SH ERRORS
 .SH STANDARDS
 POSIX.1-2008.
 .SH HISTORY
-POSIX.1-2001.
+POSIX.1-2001 (but optional).
+POSIX.1-2008.
+.PP
+Before POSIX.1-2008,
+systems on which
+.BR sched_yield ()
+is available defined
+.B _POSIX_PRIORITY_SCHEDULING
+in
+.IR <unistd.h> .
 .SH NOTES
 If the calling thread is the only thread in the highest
 priority list at that time,
 it will continue to run after a call to
 .BR sched_yield ().
 .PP
-POSIX systems on which
-.BR sched_yield ()
-is available define
-.B _POSIX_PRIORITY_SCHEDULING
-in
-.IR <unistd.h> .
-.PP
 Strategic calls to
 .BR sched_yield ()
 can improve performance by giving other threads or processes
-- 
2.40.1


  reply	other threads:[~2023-05-03 17:04 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-03 17:03 [PATCH 0/3] Discourage sched_yield(2) Alejandro Colomar
2023-05-03 17:03 ` Alejandro Colomar [this message]
2023-05-03 17:03 ` [PATCH 2/3] sched_yield.2: NOTES: Remove misleading sentence Alejandro Colomar
2023-05-03 17:03 ` [PATCH 3/3] sched_yield.2: Rename NOTES to CAVEATS, and reorder contents Alejandro Colomar

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20230503170353.25998-2-alx@kernel.org \
    --to=alx.manpages@gmail.com \
    --cc=a.clayton@nginx.com \
    --cc=alx@kernel.org \
    --cc=andrew@digital-domain.net \
    --cc=linux-man@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox