Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1521283
| From | Viresh Kumar <viresh.kumar@linaro.org> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [PATCH 1/3] cpufreq: schedutil: enable fast switch earlier |
| Date | 2016-11-14 05:20 +0100 |
| Message-ID | <sDgUp-1Sy-1@gated-at.bofh.it> (permalink) |
| References | <sChfQ-35W-17@gated-at.bofh.it> <sChfQ-35W-15@gated-at.bofh.it> <sCs1A-1sJ-25@gated-at.bofh.it> <sCyTo-653-3@gated-at.bofh.it> <sD4gy-1xq-15@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On 13-11-16, 15:46, Rafael J. Wysocki wrote: > That's only going to happen in the next patch, though, right? It > wouldn't hurt to write that in the changelog too. Sure. > Besides, I'm not actually sure if starting/stopping the kthread in > sugov_policy_alloc/free() is a good idea. It sort of conflates the > allocation of memory with kthread creation. Any chance to untangle > that? Hmm, so either I can create two new routines for the thread and call them along with alloc/free. Or I can rename the alloc/free routines and keep this patch as is. -- viresh
Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Re: [PATCH 1/3] cpufreq: schedutil: enable fast switch earlier "Rafael J. Wysocki" <rafael@kernel.org> - 2016-11-11 23:00 +0100
Re: [PATCH 1/3] cpufreq: schedutil: enable fast switch earlier Viresh Kumar <viresh.kumar@linaro.org> - 2016-11-12 06:20 +0100
Re: [PATCH 1/3] cpufreq: schedutil: enable fast switch earlier "Rafael J. Wysocki" <rafael@kernel.org> - 2016-11-13 15:50 +0100
Re: [PATCH 1/3] cpufreq: schedutil: enable fast switch earlier Viresh Kumar <viresh.kumar@linaro.org> - 2016-11-14 05:20 +0100
Re: [PATCH 1/3] cpufreq: schedutil: enable fast switch earlier Viresh Kumar <viresh.kumar@linaro.org> - 2016-11-14 12:40 +0100
csiph-web