public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dario Faggioli <raistlin@linux.it>
To: Ulrich Drepper <drepper@redhat.com>
Cc: linux-kernel@vger.kernel.org,
	Peter Zijlstra <a.p.zijlstra@chello.nl>,
	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 16:25:48 +0200	[thread overview]
Message-ID: <1218464748.6450.34.camel@Palanthas> (raw)
In-Reply-To: <48A0487B.7080600@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 1866 bytes --]

On Mon, 2008-08-11 at 07:11 -0700, Ulrich Drepper wrote:
> I'm not commenting on the code or usefulness of ht features.  I just
> want to point out a problem.
Ok...

> The authors of that POSIX extension unfortunately decided to extend the
> sched_param structure.  If you look at the definition of that structure
> Linux uses you'll see that there is no place for this.  I.e., any
> implementation of that feature following the POSIX spec to the letter
> will introduce major headache in the form of binary incompatibility.
Yeah, I'm aware of that, as you can see in the comments inside the patch
(has the mail with the patch arrived? It seems no to me :-().

> In case the features is useful enough (I actually always thought it
> isn't an have actually proposed to remove it again from POSIX)
Uao... Thanks for your support! :-P

> then I
> would rather prefer to not claim support for this feature in the POSIX
> way.  One could still implement it as described.  But change the
> interface to not require the sched_param change.
It could be done like this, I agree, for sure.

I would be sorry if we implemented this but we still miss POSIX
support... But I can't imagine any other solution that is not going
cause ABI issues too.

Anyway, thanks a lot for replying.
Dario

-- 
<<This happens because I choose it to happen!>>
(Raistlin Majere, DragonLance Chronicles -Dragons of Spring Drawning-)
----------------------------------------------------------------------
Dario Faggioli
GNU/Linux Registered User: #340657
Web: http://www.linux.it/~raistlin
Blog: http://blog.linux.it/raistlin
SIP Account: dario.faggioli@sipproxy.wengo.fr or
             raistlin@ekiga.net
Jabber Account: dario.faggioli@jabber.org/WengoPhone
GnuPG Key ID: 4DC83AC4
GnuPG Key Fingerprint: 2A78 AD5D B9CF A082 0836 08AD 9385 DA04 4DC8 3AC4

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2008-08-11 14:26 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 [this message]
2008-08-11 14:25   ` Peter Zijlstra
2008-08-11 16:23     ` Dario Faggioli
2008-08-11 16:30       ` Peter Zijlstra
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=1218464748.6450.34.camel@Palanthas \
    --to=raistlin@linux.it \
    --cc=a.p.zijlstra@chello.nl \
    --cc=akpm@osdl.org \
    --cc=drepper@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --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