Messages in this thread | | | Date | Tue, 29 Jun 2004 01:04:22 +1000 | From | Con Kolivas <> | Subject | Re: Nice 19 process still gets some CPU |
| |
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Timothy Miller wrote: | Given how much I've read here about schedulers, I should probably be | able to answer this question myself, but I just thought I might talk to | the experts. | | I'm running SETI@Home, and it has a nice value of 19. Everything else, | for the most part, is at zero. | | I'm running kernel gentoo-dev-sources-2.6.7-r6 (I believe). | | When I'm not running SETI@Home, compiler threads (emerge of a package, | kernel compile, etc.) get 100% CPU. When I AM running SETI@Home, | SETI@Home still manages to get between 5% and 10% CPU. | | I would expect that nice 0 processes should get SO MUCH more than nice | 19 processes that the nice 19 process would practically starve (and in | the case of a nice 19 process, I think starvation by nice 0 processes is | just fine), but it looks like it's not starving. | | Why is that?
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.
Con -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFA4DN2ZUg7+tp6mRURAul+AJ4v3CXwD/XZtjarmTCo7ntISETHdACfYIWT MdJ8lxP3+Z/A4tTipWSDlgA= =MeGN -----END PGP SIGNATURE----- - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |