From: Christoph Lameter <cl@linux.com>
To: gilad@benyossef.com
Cc: linux-mm@kvack.org, ghaskins@londonstockexchange.com,
niv@us.ibm.com, "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
kravetz@us.ibm.com
Subject: Re: vmstat kthreads
Date: Tue, 18 Jun 2013 17:46:50 +0000 [thread overview]
Message-ID: <0000013f58656ee7-8bb24ac4-72fa-4c0b-b888-7c056f261b6e-000000@email.amazonses.com> (raw)
In-Reply-To: <20130618152302.GA10702@linux.vnet.ibm.com>
On Tue, 18 Jun 2013, Paul E. McKenney wrote:
> I have been digging around the vmstat kthreads a bit, and it appears to
> me that there is no reason to run a given CPU's vmstat kthread unless
> that CPU spends some time executing in the kernel. If correct, this
> observation indicates that one way to safely reduce OS jitter due to the
> vmstat kthreads is to prevent them from executing on a given CPU if that
> CPU has been executing in usermode since the last time that this CPU's
> vmstat kthread executed.
Right and we have patches to that effect.
> Does this seem like a sensible course of action, or did I miss something
> when I went through the code?
Nope you are right on.
Gilad Ben-Yossef has been posting patches that address this issue in Feb
2012. Ccing him. Can we see your latest work, Gilead?
--
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:[~2013-06-18 17:46 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-18 15:23 Paul E. McKenney
2013-06-18 17:46 ` Christoph Lameter [this message]
2013-06-18 18:26 ` Paul E. McKenney
2013-06-19 14:23 ` Christoph Lameter
2013-06-19 14:50 ` Gilad Ben-Yossef
2013-06-19 14:57 ` Gilad Ben-Yossef
2013-06-20 5:06 ` Gilad Ben-Yossef
2013-06-19 14:59 ` Paul E. McKenney
2013-06-19 20:18 ` Christoph Lameter
2013-06-19 20:02 ` [PATCH v2 1/2] mm: make vmstat_update periodic run conditional Gilad Ben-Yossef
2013-06-20 14:05 ` Christoph Lameter
2013-08-07 18:16 ` Christoph Lameter
2013-08-08 6:28 ` Gilad Ben-Yossef
2013-08-08 6:54 ` Gilad Ben-Yossef
2013-08-08 14:59 ` Christoph Lameter
2013-08-09 18:56 ` Gilad Ben-Yossef
2013-08-28 19:28 ` Christoph Lameter
2013-06-19 20:02 ` [PATCH v2 2/2] mm: add sysctl to pick vmstat monitor cpu Gilad Ben-Yossef
2013-06-20 13:58 ` 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=0000013f58656ee7-8bb24ac4-72fa-4c0b-b888-7c056f261b6e-000000@email.amazonses.com \
--to=cl@linux.com \
--cc=ghaskins@londonstockexchange.com \
--cc=gilad@benyossef.com \
--cc=kravetz@us.ibm.com \
--cc=linux-mm@kvack.org \
--cc=niv@us.ibm.com \
--cc=paulmck@linux.vnet.ibm.com \
/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