Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1349453
| From | Thomas Gleixner <tglx@linutronix.de> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [PATCH] sched: Allow per-cpu kernel threads to run on online && !active |
| Date | 2016-03-03 18:50 +0100 |
| Message-ID | <r8FxV-29v-31@gated-at.bofh.it> (permalink) |
| References | <r7Upk-2rl-23@gated-at.bofh.it> <r8zVw-6xi-23@gated-at.bofh.it> <r8A5d-6Bm-43@gated-at.bofh.it> <r8A5d-6Bm-41@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On Thu, 3 Mar 2016, Thomas Gleixner wrote: > On Thu, 3 Mar 2016, Peter Zijlstra wrote: > > > +++ b/kernel/sched/core.c > > > @@ -5726,23 +5726,6 @@ static int sched_cpu_active(struct notif > > > case CPU_STARTING: > > > set_cpu_rq_start_time(); > > > > If we stick that in notify_starting() we can kill all of this. > > Yep. I'm going to kill that one by one :) After I'm done fixing the wreckage which is caused by moving set_active() alone. The numa and cpuset muck rely on it .... But now that we can delay random workload on the upcoming/outgoing cpu we can move that stuff alltogether. Thanks, tglx
Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
[PATCH] sched: Allow per-cpu kernel threads to run on online && !active Peter Zijlstra <peterz@infradead.org> - 2016-03-01 16:30 +0100
Re: [PATCH] sched: Allow per-cpu kernel threads to run on online && !active Thomas Gleixner <tglx@linutronix.de> - 2016-03-03 12:50 +0100
Re: [PATCH] sched: Allow per-cpu kernel threads to run on online && !active Thomas Gleixner <tglx@linutronix.de> - 2016-03-03 13:00 +0100
Re: [PATCH] sched: Allow per-cpu kernel threads to run on online && !active Thomas Gleixner <tglx@linutronix.de> - 2016-03-03 18:50 +0100
Re: [PATCH] sched: Allow per-cpu kernel threads to run on online && !active Peter Zijlstra <peterz@infradead.org> - 2016-03-03 13:00 +0100
csiph-web