[lkml]   [2007]   [Mar]   [12]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: [PATCH][RSDL-mm 0/7] RSDL cpu scheduler for 2.6.21-rc3-mm2
    On 13/03/07, Mike Galbraith <> wrote:
    > On Tue, 2007-03-13 at 07:38 +1100, Con Kolivas wrote:
    > > On Tuesday 13 March 2007 07:11, Mike Galbraith wrote:
    > > >
    > > > Killing the known corner case starvation scenarios is wonderful, but
    > > > let's not just pretend that interactive tasks don't have any special
    > > > requirements.
    > >
    > > Now you're really making a stretch of things. Where on earth did I say that
    > > interactive tasks don't have special requirements? It's a fundamental feature
    > > of this scheduler that I go to great pains to get them as low latency as
    > > possible and their fair share of cpu despite having a completely fair cpu
    > > distribution.
    > As soon as your cpu is fully utilized, fairness looses or interactivity
    > loses. Pick one.

    That's not true unless you refuse to prioritise your tasks
    accordingly. Let's take this discussion in a different direction. You
    already nice your lame processes. Why? You already have the concept
    that you are prioritising things to normal or background tasks. You
    say so yourself that lame is a background task. Stating the bleedingly
    obvious, the unix way of prioritising things is via nice. You already
    do that. So moving on from that...

    Your test case you ask "how can I maximise cpu usage". Well you know
    the answer already. You run two threads. I won't dispute that.

    The debate seems to be centered on whether two tasks that are niced +5
    or to a higher value is background. In my opinion, nice 5 is not
    background, but relatively less cpu. You already are savvy enough to
    be using two threads and nicing them. All I ask you to do when using
    RSDL is to change your expectations slightly and your settings from
    nice 5 to nice 10 or 15 or even 19. Why is that so offensive to you?
    nice 5 is 75% the cpu of nice 0. nice 10 is 50%, nice 15 is 25%, nice
    19 is 5%.If you're so intent on defining nice 5 as background would it
    be a matter of me just modifying nice 5 to be 25% instead? I suspect
    your answer will be no because then you'll argue that you shouldn't
    nice at all, but it should be interesting to see your response. You
    seem to be advocating that the scheduler does everything and we need
    to implement some complex flag instead. I don't believe that's the
    right thing to do at all. So I offer you some options.

    1. Be happy with changing your nice from 5 to15. I still don't think
    this is in any way unreasonable.
    2. Wait for me to fix -niced tasks behaviour and -nice your X. I plan
    to implement this change anyway, not necessarily for X.
    3. Have me redefine what nice 5 is, and tell me what percentage cpu
    you think is right.
    4. Any combination of the above.

    Please don't pick 5.none of the above. Please try to work with me on this.

    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to
    More majordomo info at
    Please read the FAQ at

     \ /
      Last update: 2007-03-12 23:53    [W:0.313 / U:8.144 seconds]
    ©2003-2017 Jasper Spaans. hosted at Digital OceanAdvertise on this site