linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Shiraz Hashim <shiraz.linux.kernel@gmail.com>
To: Christoph Lameter <cl@linux.com>
Cc: Michal Hocko <mhocko@kernel.org>,
	akpm@linux-foundation.org, linux-mm@kvack.org,
	LKML <linux-kernel@vger.kernel.org>,
	hannes@cmpxchg.org, penguin-kernel@i-love.sakura.ne.jp
Subject: Re: vmstat: make vmstat_updater deferrable again and shut down on idle
Date: Wed, 20 Jan 2016 19:22:09 +0530	[thread overview]
Message-ID: <CAPub148GRFho0oS9Vf0UdX+2Q84+031DE7jKj6Nxc0o0ZqWEmA@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.20.1512101441140.19122@east.gentwo.org>

Hi Christoph,

On Fri, Dec 11, 2015 at 2:15 AM, Christoph Lameter <cl@linux.com> wrote:
> Currently the vmstat updater is not deferrable as a result of commit
> ba4877b9ca51f80b5d30f304a46762f0509e1635. This in turn can cause multiple
> interruptions of the applications because the vmstat updater may run at
> different times than tick processing. No good.
>
> Make vmstate_update deferrable again and provide a function that
> folds the differentials when the processor is going to idle mode thus
> addressing the issue of the above commit in a clean way.
>

The patch makes vmstat_shepherd deferable which if is quiesed
would not schedule vmstat update on other cpus. Wouldn't this
aggravate the problem of vmstat for rest cpus not gettng updated.

regards
Shiraz

--
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>

  parent reply	other threads:[~2016-01-20 13:52 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-10 20:45 Christoph Lameter
2015-12-10 23:31 ` Andrew Morton
2015-12-11  1:41   ` Christoph Lameter
2015-12-14 18:32     ` Christoph Lameter
2016-01-20 13:52 ` Shiraz Hashim [this message]
2016-01-20 15:12   ` Christoph Lameter
2016-01-21  6:24     ` Shiraz Hashim
2016-01-21 15:41       ` Christoph Lameter

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=CAPub148GRFho0oS9Vf0UdX+2Q84+031DE7jKj6Nxc0o0ZqWEmA@mail.gmail.com \
    --to=shiraz.linux.kernel@gmail.com \
    --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=mhocko@kernel.org \
    --cc=penguin-kernel@i-love.sakura.ne.jp \
    /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