Re: loop-aes nice value

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



I see, why do we need to have the highest priority possible for the loop 
device? and why does -20 just work fine for normal kernels?
cheers,
greg
At 18:01 2002. 10. 14.­, you wrote:
>Newsmail wrote:
> > Hi Jari, I saw that you changed the default nice value for the loop device
> > when the kernel is using mingo's sched. If I remember that value was -9.
> > Did you choose '-9' as a + - arbitrary value under 0, but over -20, or it
> > has some special reason to be -9 and not -5 for exemple?
>
>I read Ingo's O(1) scheduler comments from kernel source. Process' nice is
>dynamically adjusted -5...+5 based on how it has behaved in past. So, I
>first tested with nice -5. Interactivity was OK with that. I kept increasing
>priority until bad interactivity appeared at nice -10, so I chose -9.
>Temporary bad interactivity still appeared at -9, but at -10 it was
>sustained bad interactivity.
>
>Regards,
>Jari Ruusu <jari.ruusu@pp.inet.fi>


-
Linux-crypto:  cryptography in and on the Linux system
Archive:       http://mail.nl.linux.org/linux-crypto/


[Index of Archives]     [Kernel]     [Linux Crypto]     [Gnu Crypto]     [Gnu Classpath]     [Netfilter]     [Bugtraq]
  Powered by Linux