public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Florian Weimer <fweimer@redhat.com>
To: Carlos O'Donell <carlos@redhat.com>
Cc: libc-alpha@sourceware.org
Subject: Re: [PATCH] manual: Document lack of conformance of sched_* functions [BZ #14829]
Date: Wed, 09 Jan 2019 12:31:00 -0000	[thread overview]
Message-ID: <875zuyui68.fsf@oldenburg2.str.redhat.com> (raw)
In-Reply-To: <87efajg4c3.fsf@oldenburg2.str.redhat.com> (Florian Weimer's message of "Fri, 14 Dec 2018 22:56:28 +0100")

* Florian Weimer:

> * Carlos O'Donell:
>
>> My preference is to add a trailing "(See bug 14829)", since finding that
>> bug helps readers see what's going on.
>
> Sure.  Please see the patch below.
>
> Thanks,
> Florian
>
> -----
> On Linux, we define _POSIX_PRIORITY_SCHEDULING, but functions such
> as sched_setparam and sched_setscheduler apply to individual threads,
> not processes.
>
> 2018-12-14  Florian Weimer  <fweimer@redhat.com>
>
> 	[BZ #14829]
> 	* manual/resource.texi (Basic Scheduling Functions): Add
> 	portability note.  Change process to task throughout the section.
> 	Remove incorrect comment about sched_yield as it affects
> 	tasks/threads, not entire processes.
> 	* sysdeps/unix/sysv/linux/bits/posix_opt.h
> 	(_POSIX_PRIORITY_SCHEDULING): Update comment.

Ping?  <https://sourceware.org/ml/libc-alpha/2018-12/msg00516.html>

Thanks,
Florian

  reply	other threads:[~2019-01-09 12:31 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-07 13:01 Florian Weimer
2018-12-14 20:57 ` Carlos O'Donell
2018-12-14 21:09   ` Florian Weimer
2018-12-14 21:20     ` Carlos O'Donell
2018-12-14 22:30       ` Florian Weimer
2019-01-09 12:31         ` Florian Weimer [this message]
2019-01-09 16:14         ` Carlos O'Donell

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=875zuyui68.fsf@oldenburg2.str.redhat.com \
    --to=fweimer@redhat.com \
    --cc=carlos@redhat.com \
    --cc=libc-alpha@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).