From: Michal Hocko <mhocko@suse.cz>
To: Christoph Lameter <cl@linux.com>
Cc: Vinayak Menon <vinmenon@codeaurora.org>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
akpm@linux-foundation.org, hannes@cmpxchg.org,
vdavydov@parallels.com, mgorman@suse.de, minchan@kernel.org
Subject: Re: [PATCH v2] mm: vmscan: fix the page state calculation in too_many_isolated
Date: Fri, 30 Jan 2015 16:27:50 +0100 [thread overview]
Message-ID: <20150130152750.GH15505@dhcp22.suse.cz> (raw)
In-Reply-To: <alpine.DEB.2.11.1501291131510.22780@gentwo.org>
On Thu 29-01-15 11:32:43, Christoph Lameter wrote:
[...]
> Subject: vmstat: Reduce time interval to stat update on idle cpu
>
> It was noted that the vm stat shepherd runs every 2 seconds and
> that the vmstat update is then scheduled 2 seconds in the future.
>
> This yields an interval of double the time interval which is not
> desired.
>
> Change the shepherd so that it does not delay the vmstat update
> on the other cpu. We stil have to use schedule_delayed_work since
> we are using a delayed_work_struct but we can set the delay to 0.
>
>
> Signed-off-by: Christoph Lameter <cl@linux.com>
Acked-by: Michal Hocko <mhocko@suse.cz>
>
> Index: linux/mm/vmstat.c
> ===================================================================
> --- linux.orig/mm/vmstat.c
> +++ linux/mm/vmstat.c
> @@ -1435,8 +1435,8 @@ static void vmstat_shepherd(struct work_
> if (need_update(cpu) &&
> cpumask_test_and_clear_cpu(cpu, cpu_stat_off))
>
> - schedule_delayed_work_on(cpu, &per_cpu(vmstat_work, cpu),
> - __round_jiffies_relative(sysctl_stat_interval, cpu));
> + schedule_delayed_work_on(cpu,
> + &per_cpu(vmstat_work, cpu), 0);
>
> put_online_cpus();
>
--
Michal Hocko
SUSE Labs
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2015-01-30 15:27 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-14 11:36 Vinayak Menon
2015-01-14 16:50 ` Michal Hocko
2015-01-15 17:24 ` Vinayak Menon
2015-01-16 15:49 ` Michal Hocko
2015-01-16 17:57 ` Michal Hocko
2015-01-16 19:17 ` Christoph Lameter
2015-01-17 15:18 ` Vinayak Menon
2015-01-17 19:48 ` Christoph Lameter
2015-01-19 4:27 ` Vinayak Menon
2015-01-21 14:39 ` Michal Hocko
2015-01-22 15:16 ` Vlastimil Babka
2015-01-22 16:11 ` Christoph Lameter
2015-01-26 17:46 ` Michal Hocko
2015-01-26 18:35 ` Christoph Lameter
2015-01-27 10:52 ` Michal Hocko
2015-01-27 16:59 ` Christoph Lameter
2015-01-30 15:28 ` Michal Hocko
2015-01-26 17:28 ` Michal Hocko
2015-01-26 18:35 ` Christoph Lameter
2015-01-26 22:11 ` Andrew Morton
2015-01-27 10:41 ` Michal Hocko
2015-01-27 10:33 ` Vinayak Menon
2015-01-27 10:45 ` Michal Hocko
2015-01-29 17:32 ` Christoph Lameter
2015-01-30 15:27 ` Michal Hocko [this message]
2015-01-16 1:17 ` Andrew Morton
2015-01-16 5:10 ` Vinayak Menon
2015-01-17 16:29 ` Vinayak Menon
2015-02-11 22:14 ` Andrew Morton
2015-02-12 16:19 ` Vlastimil Babka
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20150130152750.GH15505@dhcp22.suse.cz \
--to=mhocko@suse.cz \
--cc=akpm@linux-foundation.org \
--cc=cl@linux.com \
--cc=hannes@cmpxchg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@suse.de \
--cc=minchan@kernel.org \
--cc=vdavydov@parallels.com \
--cc=vinmenon@codeaurora.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox