Re: [RFC PATCH v2 4/8] tick/nohz: keep tick on for a fast idle

On 2017/10/16 14:25, Mike Galbraith wrote: > On Mon, 2017-10-16 at 13:34 +0800, Li, Aubrey wrote: >> On 2017/10/16 12:45, Mike Galbraith wrote: >>> On Mon, 2017-10-16 at 11:26 +0800, Li, Aubrey wrote: I'll try to move quiet_vmstat() into the normal idle branch if this patch series

Re: [RFC PATCH v2 4/8] tick/nohz: keep tick on for a fast idle

On 2017/10/16 14:25, Mike Galbraith wrote: > On Mon, 2017-10-16 at 13:34 +0800, Li, Aubrey wrote: >> On 2017/10/16 12:45, Mike Galbraith wrote: >>> On Mon, 2017-10-16 at 11:26 +0800, Li, Aubrey wrote: I'll try to move quiet_vmstat() into the normal idle branch if this patch series

Re: [RFC PATCH v2 4/8] tick/nohz: keep tick on for a fast idle

On Mon, 2017-10-16 at 13:34 +0800, Li, Aubrey wrote: > On 2017/10/16 12:45, Mike Galbraith wrote: > > On Mon, 2017-10-16 at 11:26 +0800, Li, Aubrey wrote: > >> > >> I'll try to move quiet_vmstat() into the normal idle branch if this patch > >> series > >> are reasonable. Is fast_idle a good

Re: [RFC PATCH v2 4/8] tick/nohz: keep tick on for a fast idle

On Mon, 2017-10-16 at 13:34 +0800, Li, Aubrey wrote: > On 2017/10/16 12:45, Mike Galbraith wrote: > > On Mon, 2017-10-16 at 11:26 +0800, Li, Aubrey wrote: > >> > >> I'll try to move quiet_vmstat() into the normal idle branch if this patch > >> series > >> are reasonable. Is fast_idle a good

Re: [RFC PATCH v2 4/8] tick/nohz: keep tick on for a fast idle

On 2017/10/16 12:45, Mike Galbraith wrote: > On Mon, 2017-10-16 at 11:26 +0800, Li, Aubrey wrote: >> >> I'll try to move quiet_vmstat() into the normal idle branch if this patch >> series >> are reasonable. Is fast_idle a good indication for it? > > see x86_tip 62cb1188ed86 sched/idle: Move

Re: [RFC PATCH v2 4/8] tick/nohz: keep tick on for a fast idle

On 2017/10/16 12:45, Mike Galbraith wrote: > On Mon, 2017-10-16 at 11:26 +0800, Li, Aubrey wrote: >> >> I'll try to move quiet_vmstat() into the normal idle branch if this patch >> series >> are reasonable. Is fast_idle a good indication for it? > > see x86_tip 62cb1188ed86 sched/idle: Move

Re: [RFC PATCH v2 4/8] tick/nohz: keep tick on for a fast idle

On Mon, 2017-10-16 at 11:26 +0800, Li, Aubrey wrote: > > I'll try to move quiet_vmstat() into the normal idle branch if this patch > series > are reasonable. Is fast_idle a good indication for it? see x86_tip 62cb1188ed86 sched/idle: Move quiet_vmstate() into the NOHZ code -Mike

Re: [RFC PATCH v2 4/8] tick/nohz: keep tick on for a fast idle

On Mon, 2017-10-16 at 11:26 +0800, Li, Aubrey wrote: > > I'll try to move quiet_vmstat() into the normal idle branch if this patch > series > are reasonable. Is fast_idle a good indication for it? see x86_tip 62cb1188ed86 sched/idle: Move quiet_vmstate() into the NOHZ code -Mike

Re: [RFC PATCH v2 4/8] tick/nohz: keep tick on for a fast idle

On 2017/10/14 8:51, Rafael J. Wysocki wrote: > On Saturday, September 30, 2017 9:20:30 AM CEST Aubrey Li wrote: >> If the next idle is expected to be a fast idle, we should keep tick >> on before going into idle >> >> Signed-off-by: Aubrey Li > > This also can be

Re: [RFC PATCH v2 4/8] tick/nohz: keep tick on for a fast idle

On 2017/10/14 8:51, Rafael J. Wysocki wrote: > On Saturday, September 30, 2017 9:20:30 AM CEST Aubrey Li wrote: >> If the next idle is expected to be a fast idle, we should keep tick >> on before going into idle >> >> Signed-off-by: Aubrey Li > > This also can be merged with the previous patch

Re: [RFC PATCH v2 4/8] tick/nohz: keep tick on for a fast idle

On Saturday, September 30, 2017 9:20:30 AM CEST Aubrey Li wrote: > If the next idle is expected to be a fast idle, we should keep tick > on before going into idle > > Signed-off-by: Aubrey Li This also can be merged with the previous patch (and the [2/8]) IMO. > ---

Re: [RFC PATCH v2 4/8] tick/nohz: keep tick on for a fast idle

On Saturday, September 30, 2017 9:20:30 AM CEST Aubrey Li wrote: > If the next idle is expected to be a fast idle, we should keep tick > on before going into idle > > Signed-off-by: Aubrey Li This also can be merged with the previous patch (and the [2/8]) IMO. > --- >

[RFC PATCH v2 4/8] tick/nohz: keep tick on for a fast idle

If the next idle is expected to be a fast idle, we should keep tick on before going into idle Signed-off-by: Aubrey Li --- drivers/cpuidle/cpuidle.c | 14 ++ include/linux/cpuidle.h | 2 ++ kernel/time/tick-sched.c | 4 3 files changed, 20

[RFC PATCH v2 4/8] tick/nohz: keep tick on for a fast idle

If the next idle is expected to be a fast idle, we should keep tick on before going into idle Signed-off-by: Aubrey Li --- drivers/cpuidle/cpuidle.c | 14 ++ include/linux/cpuidle.h | 2 ++ kernel/time/tick-sched.c | 4 3 files changed, 20 insertions(+) diff --git