Re: [PATCH 1 of 3] Support of getting scheduler defaults

[Juergen Gross <juergen.gross@ts.fujitsu.com>]

On 05/23/2012 09:22 AM, Dario Faggioli wrote:
> On Wed, 2012-05-23 at 07:34 +0200, Juergen Gross wrote:
>>> #define PERIOD_MAX MILLISECS(10000) /* 10s  */
>>> #define PERIOD_MIN (MICROSECS(10))  /* 10us */
>>> #define SLICE_MIN (MICROSECS(5))    /*  5us */
>> I think this should remain in the hypervisor only.
>>
> Me too.
>
>>> Also, extratime is a flag, so I think 0 and 1 are both meaningful
>>> values, maybe we can go for -1 as for cap (I'll try and let you know).
>> Why not -1 for all values?
>>
> Would work, I guess, unless there's some collision with big weights
> represented on short unsigned value (not sure it's like that, and I've
> always been bad at this kind of math! :-P).

The -1 would be set in scparams only, and there it is an integer. It should
never be written to the "real" scheduler parameters passed to the hypervisor.


Juergen

-- 
Juergen Gross                 Principal Developer Operating Systems
PDG ES&S SWE OS6                       Telephone: +49 (0) 89 3222 2967
Fujitsu Technology Solutions              e-mail: juergen.gross@ts.fujitsu.com
Domagkstr. 28                           Internet: ts.fujitsu.com
D-80807 Muenchen                 Company details: ts.fujitsu.com/imprint.html