Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1182775
| From | Mike Galbraith <umgwanakikbuti@gmail.com> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [PATCH v2] sched: let __sched_period() use rq's nr_running |
| Date | 2015-07-13 14:40 +0200 |
| Message-ID | <pLLbB-50E-33@gated-at.bofh.it> (permalink) |
| References | (2 earlier) <pLApQ-733-3@gated-at.bofh.it> <pLG2d-23J-7@gated-at.bofh.it> <pLHrj-2LV-1@gated-at.bofh.it> <pLJ9L-3QH-7@gated-at.bofh.it> <pLJWa-4m6-27@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On Mon, 2015-07-13 at 20:07 +0900, Byungchul Park wrote: > i still think stretching with local cfs's nr_running should be replaced with > stretching with a top(=root) level one. I think we just can't take 'slice' _too_ seriously. Not only is it annoying with cgroups, the scheduler simply doesn't deliver 'slices' in the traditional sense, it equalizes vruntimes, planning to do that at slice granularity. FAIR_SLEEPERS doesn't make that planning any easier. With a pure compute load and no HR_TICK, what you get is tick granularity preemption checkpoints, but having just chewed up a 'slice' means nothing if you're still leftmost. It's all about vruntime, so leftmost can have back to back 'slices'. FAIR_SLEEPERS just increases the odds that leftmost WILL take more than one 'slice'. (we could perhaps decay deficit after a full slice or such to decrease the spread growth that sleepers induce. annoying problem, especially so with a gaggle of identical sleepers, as sleep time becomes meaningless, there is no differential to equalize.. other than the ones we create.. but I'm digressing, a lot, time to stop thinking/typing, go do work;) -Mike -- 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/
Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
[PATCH v2] sched: let __sched_period() use rq's nr_running byungchul.park@lge.com - 2015-07-10 10:20 +0200
Re: [PATCH v2] sched: let __sched_period() use rq's nr_running Mike Galbraith <umgwanakikbuti@gmail.com> - 2015-07-13 09:10 +0200
Re: [PATCH v2] sched: let __sched_period() use rq's nr_running Byungchul Park <byungchul.park@lge.com> - 2015-07-13 10:40 +0200
Re: [PATCH v2] sched: let __sched_period() use rq's nr_running Mike Galbraith <umgwanakikbuti@gmail.com> - 2015-07-13 12:30 +0200
Re: [PATCH v2] sched: let __sched_period() use rq's nr_running Byungchul Park <byungchul.park@lge.com> - 2015-07-13 13:20 +0200
Re: [PATCH v2] sched: let __sched_period() use rq's nr_running Mike Galbraith <umgwanakikbuti@gmail.com> - 2015-07-13 14:40 +0200
Re: [PATCH v2] sched: let __sched_period() use rq's nr_running Peter Zijlstra <peterz@infradead.org> - 2015-07-13 10:30 +0200
Re: [PATCH v2] sched: let __sched_period() use rq's nr_running Byungchul Park <byungchul.park@lge.com> - 2015-07-13 11:30 +0200
Re: [PATCH v2] sched: let __sched_period() use rq's nr_running Byungchul Park <byungchul.park@lge.com> - 2015-07-14 11:30 +0200
csiph-web