public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Florian Weimer <fweimer@redhat.com>
To: Len Brown via Libc-alpha <libc-alpha@sourceware.org>
Cc: "H.J. Lu" <hjl.tools@gmail.com>,  Len Brown <lenb@kernel.org>
Subject: Re: Pthread QOS interface
Date: Wed, 18 May 2022 12:19:13 +0200	[thread overview]
Message-ID: <87v8u36t3y.fsf@oldenburg.str.redhat.com> (raw)
In-Reply-To: <CAJvTdKkAu_AxrhsafK4fp4U5Bn05q5eR7BJw6kUfNRo5qiinHw@mail.gmail.com> (Len Brown via Libc-alpha's message of "Tue, 17 May 2022 13:59:05 -1000")

* Len Brown via Libc-alpha:

> I have a more specific question.
>
> Can we implement EXACTLY the same interface as Apple has -- so a
> cross-platform application doesn't have to change?  (I see an Apple
> source license on that qos.h -- is that an issue with an API?)
>
> (I think the answer about the scheduling interface is simply "yes", we
> can add new Linux-specific flags to the existing sched_setattr(2) --
> but ideally applications should be using a more portable interface,
> rather than directly invoking linux-specific system calls)

Isn't this traditionally handled by cgroups and/or rtkit?

If we can get a syscall interface for this from the kernel, we could add
something in parallel to that to glibc, but I doubt it would have the
same semantics as the Darwin interface even if we keep the API the same.
For example, Linux may require different permissions for making these
changes, and apply them to different aspects of system behavior (CPU,
mass storage I/O, memory bandwidth, network traffic).

Thanks,
Florian


  reply	other threads:[~2022-05-18 10:19 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-17 23:03 H.J. Lu
2022-05-17 23:59 ` Len Brown
2022-05-18 10:19   ` Florian Weimer [this message]
2022-05-18 20:55     ` Len Brown
2022-05-24  9:39       ` Florian Weimer

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=87v8u36t3y.fsf@oldenburg.str.redhat.com \
    --to=fweimer@redhat.com \
    --cc=hjl.tools@gmail.com \
    --cc=lenb@kernel.org \
    --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).