Re: Nice 19 process still gets some CPU

[Michael Buesch]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Quoting Chris Friesen <cfriesen@xxxxxxxxxxxxxxxxxx>:
> Timothy Miller wrote:
> > 
> > 
> > Con Kolivas wrote:
> > 
> >  >
> >  > It definitely should _not_ starve. That is the unixy way of doing
> >  > things. Everything must go forward. Around 5% cpu for nice 19 sounds
> >  > just right. If you want scheduling only when there's spare cpu cycles
> >  > you need a sched batch(idle) implementation.
> >  >
> >  >
> > 
> > Well, since I can't rewrite the app, I can't make it sched batch.  Nice
> > values are an easy thing to get at for anything that's running.
> 
> Sure you can.  You can set the scheduler policy on any process in the system, 
> while its running.
> 
> int sched_setscheduler(pid_t pid, int policy, const struct sched_param *p);
> 
> Takes about two minutes to write an equivalent to "nice" to set scheduler 
> policies and priorities.

Sounds cool. I was searching this syscall for a long time, now. :)
But batch scheduling is available in -ck only, so this works only
with -ck kernels. Correct?

> Chris

- -- 
Regards Michael Buesch  [ http://www.tuxsoft.de.vu ]


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFA4EYfFGK1OIvVOP4RAogAAKCQ8oYHshIKPXYNAVptHh1QJRRfywCfX8Cg
GxzK64XtYdtnJLReOMrzR3o=
=ithN
-----END PGP SIGNATURE-----
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/