[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <5de2c77b-0c55-5fd9-64f6-aba67f111db5@linux.intel.com>
Date: Wed, 12 Jul 2017 10:07:50 +0800
From: "Li, Aubrey" <aubrey.li@...ux.intel.com>
To: Christoph Lameter <cl@...ux.com>,
Frederic Weisbecker <fweisbec@...il.com>
Cc: Peter Zijlstra <peterz@...radead.org>,
Andi Kleen <ak@...ux.intel.com>,
Aubrey Li <aubrey.li@...el.com>, tglx@...utronix.de,
len.brown@...el.com, rjw@...ysocki.net, tim.c.chen@...ux.intel.com,
arjan@...ux.intel.com, paulmck@...ux.vnet.ibm.com,
yang.zhang.wz@...il.com, x86@...nel.org,
linux-kernel@...r.kernel.org
Subject: Re: [RFC PATCH v1 00/11] Create fast idle path for short idle periods
On 2017/7/12 1:58, Christoph Lameter wrote:
> On Tue, 11 Jul 2017, Frederic Weisbecker wrote:
>
>>> --- a/kernel/time/tick-sched.c
>>> +++ b/kernel/time/tick-sched.c
>>> @@ -787,6 +787,7 @@ static ktime_t tick_nohz_stop_sched_tick(struct tick_sched *ts,
>>> if (!ts->tick_stopped) {
>>> calc_load_nohz_start();
>>> cpu_load_update_nohz_start();
>>> + quiet_vmstat();
>>
>> This patch seems to make sense. Christoph?
>
> Ok makes sense to me too. Was never entirely sure where the proper place
> would be to call it.
>
Do we have another path to invoke tick_nohz_stop_sched_tick() in the interrupt exit context
for nohz full case?
Thanks,
-Aubrey
Powered by blists - more mailing lists