From: Patrick Bellasi <patrick.bellasi@arm.com>
To: Juri Lelli <juri.lelli@redhat.com>
Cc: Joseph Myers <joseph@codesourcery.com>,
Florian Weimer <fw@deneb.enyo.de>,
Szabolcs Nagy <szabolcs.nagy@arm.com>,
nd@arm.com, libc-alpha@sourceware.org
Subject: Re: Is adding a pthread wrapper for sched_{get,set}attr feasible?
Date: Fri, 24 Aug 2018 13:09:12 +0100 [thread overview]
Message-ID: <20180824120912.GG2971@e110439-lin> (raw)
In-Reply-To: <20180824064552.GA24860@localhost.localdomain>
Hi Juri,
On 24-Aug 08:45, Juri Lelli wrote:
> Hi,
thanks for CCing me!
> On 23/08/18 19:50, Joseph Myers wrote:
> > On Thu, 23 Aug 2018, Juri Lelli wrote:
> >
> > > One could also look at a proposed extension that is currently under
> > > review (utilclamp [2]) to have an idea of how future further extensions
> > > will be handled.
> >
> > I don't see any recent discussion of that on linux-api; please remind the
> > people involved that all extensions to the kernel/userspace API should go
> > through linux-api if they are to be properly reviewed and problems found
> > before they get into the kernel.
Sorry guys, my bad... didn't know about that requirement.
We definitively need a proper review for the user-space API.
> Ah, good point.
>
> Let me Cc Patrick (who is driving the discussion) so he can do that for
> next versions.
I'll add linux-api to the next v4 posting.
Does that list cover also usages related to cgroups?
Best,
Patrick
--
#include <best/regards.h>
Patrick Bellasi
next prev parent reply other threads:[~2018-08-24 12:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-22 13:15 Is adding a pthread wrapper for sched_{get,set}attr feasible? Juri Lelli
2018-08-22 14:03 ` Szabolcs Nagy
2018-08-22 14:32 ` Juri Lelli
2018-08-22 14:37 ` Szabolcs Nagy
2018-08-22 21:00 ` Florian Weimer
2018-08-23 7:31 ` Juri Lelli
2018-08-23 19:50 ` Joseph Myers
2018-08-24 6:45 ` Juri Lelli
2018-08-24 12:09 ` Patrick Bellasi [this message]
2018-08-24 14:43 ` Joseph Myers
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
List information: https://www.gnu.org/software/libc/involved.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180824120912.GG2971@e110439-lin \
--to=patrick.bellasi@arm.com \
--cc=fw@deneb.enyo.de \
--cc=joseph@codesourcery.com \
--cc=juri.lelli@redhat.com \
--cc=libc-alpha@sourceware.org \
--cc=nd@arm.com \
--cc=szabolcs.nagy@arm.com \
/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).