lkml.org 
[lkml]   [2010]   [Nov]   [10]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    SubjectRe: [RFC][PATCH 02/22] sched: add extended scheduling interface
    From
    Date
    On Wed, 2010-11-10 at 18:28 +0100, Peter Zijlstra wrote:
    > On Fri, 2010-10-29 at 08:27 +0200, Raistlin wrote:
    > > +struct sched_param_ex {
    > > + int sched_priority;
    > > + struct timespec sched_runtime;
    > > + struct timespec sched_deadline;
    > > + struct timespec sched_period;
    > > + unsigned int sched_flags;
    > > +
    > > + struct timespec curr_runtime;
    > > + struct timespec used_runtime;
    > > + struct timespec curr_deadline;
    > > +};
    >
    > I would suggest we add at least one more field so we can implement the
    > stochastic model from UNC, sched_runtime_dev or sched_runtime_var or
    > somesuch.
    >
    Moreover, I really think that the capability of reporting back current
    and used runtime (and deadline) would be very useful for implementing
    more complex (and effective) scheduling behaviour in userspace... And in
    fact I added them here.

    Something I was not so sure, and thus about what I wanted your opinion,
    was if I should put these things here --so that they are retrievable by
    a sched_getparam[_ex, 2], or either add yet another syscall specific for
    that? Thoughts?

    Thanks,
    Dario
    --
    <<This happens because I choose it to happen!>> (Raistlin Majere)
    ----------------------------------------------------------------------
    Dario Faggioli, ReTiS Lab, Scuola Superiore Sant'Anna, Pisa (Italy)

    http://blog.linux.it/raistlin / raistlin@ekiga.net /
    dario.faggioli@jabber.org
    [unhandled content-type:application/pgp-signature]
    \
     
     \ /
      Last update: 2010-11-10 23:27    [W:2.415 / U:0.096 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site