From: Peter Zijlstra <a.p.zijlstra@chello.nl>
To: Dario Faggioli <raistlin@linux.it>
Cc: Ulrich Drepper <drepper@redhat.com>,
linux-kernel@vger.kernel.org, Ingo Molnar <mingo@elte.hu>,
Thomas Gleixner <tglx@linutronix.de>,
Steven Rostedt <rostedt@goodmis.org>,
Andrew Morton <akpm@osdl.org>
Subject: Re: [RFC 0/1][PATCH] POSIX SCHED_SPORADIC implementation for tasks and groups
Date: Mon, 11 Aug 2008 18:30:52 +0200 [thread overview]
Message-ID: <1218472252.10800.107.camel@twins> (raw)
In-Reply-To: <1218471794.6450.87.camel@Palanthas>
On Mon, 2008-08-11 at 18:23 +0200, Dario Faggioli wrote:
> On Mon, 2008-08-11 at 16:25 +0200, Peter Zijlstra wrote:
> > My suggestion would be to create struct sched_param2 with plenty of
> > padding to support future expansion and add
> > sys_sched_setscheduler2()/sys_sched_getscheduler2() to deal with this
> > new structure.
> And we will miss POSIX compliance. :-(
> Anyway, I agree the ABI issue this could raise are serious enough and, I
> repeat, I can't see any other solution too.
Well, a new version of glibc could use those to implement the posix
interface. Because as I understand it, glibc can break ABI on certain
version bumps.
next prev parent reply other threads:[~2008-08-11 16:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-11 13:49 [RFC 0/1][PATCH] POSIX SCHED_SPORADIC implementation for tasks and groups Dario Faggioli
2008-08-11 14:11 ` Ulrich Drepper
2008-08-11 14:25 ` Dario Faggioli
2008-08-11 14:25 ` Peter Zijlstra
2008-08-11 16:23 ` Dario Faggioli
2008-08-11 16:30 ` Peter Zijlstra [this message]
2008-08-11 16:49 ` Dario Faggioli
2008-08-11 17:17 ` Ulrich Drepper
2008-08-17 22:27 ` Dario Faggioli
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=1218472252.10800.107.camel@twins \
--to=a.p.zijlstra@chello.nl \
--cc=akpm@osdl.org \
--cc=drepper@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=raistlin@linux.it \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
/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