From: Christoph Lameter <cl@linux.com>
To: Joonsoo Kim <iamjoonsoo.kim@lge.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [PATCH] mm/vmstat: retrieve more accurate vmstat value
Date: Wed, 25 Nov 2015 10:04:44 -0600 (CST) [thread overview]
Message-ID: <alpine.DEB.2.20.1511251002380.31590@east.gentwo.org> (raw)
In-Reply-To: <20151125025735.GC9563@js1304-P5Q-DELUXE>
On Wed, 25 Nov 2015, Joonsoo Kim wrote:
> I think that maintaining duplicate counter to guarantee accuracy isn't
> reasonable solution. It would cause more overhead to the system.
Simply remove the counter from the vmstat handling and do it differently
then.
> Although vmstat values aren't designed for accuracy, these are already
> used by some sensitive places so it is better to be more accurate.
The design is to sacrifice accuracy and the time the updates occur for
performance reasons. This is not the purpose the counters were designed
for. If you put these demands on the vmstat then you will get complex
convoluted code and compromise performance.
> What this patch does is just adding current cpu's diff to global value
> when retrieving in order to get more accurate value and this would not be
> expensive. I think that it doesn't break any design principle of vmstat.
There have been a number of expectations recently regarding the accuracy
of vmstat. We are on the wrong track here.
--
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-11-25 16:04 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-24 6:22 Joonsoo Kim
2015-11-24 15:36 ` Christoph Lameter
2015-11-25 2:57 ` Joonsoo Kim
2015-11-25 16:04 ` Christoph Lameter [this message]
2015-11-25 18:03 ` Michal Hocko
2015-11-25 18:26 ` Christoph Lameter
2015-11-26 1:52 ` Joonsoo Kim
2015-12-03 4:14 ` Joonsoo Kim
2016-01-27 23:13 ` David Rientjes
2016-01-28 5:08 ` Joonsoo Kim
2015-11-25 12:00 ` Michal Hocko
2015-11-25 13:43 ` Vlastimil Babka
2015-11-25 13:47 ` Michal Hocko
2015-11-26 1:56 ` Joonsoo Kim
2015-11-26 5:03 ` vinayak menon
2015-11-26 15:03 ` Michal Hocko
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=alpine.DEB.2.20.1511251002380.31590@east.gentwo.org \
--to=cl@linux.com \
--cc=akpm@linux-foundation.org \
--cc=iamjoonsoo.kim@lge.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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