mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Michal Hocko <mhocko@kernel.org>
To: Pintu Kumar <pintu.k@samsung.com>
Cc: akpm@linux-foundation.org, linux-kernel@vger.kernel.org,
	linux-mm@kvack.org, minchan@kernel.org, dave@stgolabs.net,
	koct9i@gmail.com, mgorman@suse.de, vbabka@suse.cz,
	js1304@gmail.com, hannes@cmpxchg.org,
	alexander.h.duyck@redhat.com, sasha.levin@oracle.com,
	cl@linux.com, fengguang.wu@intel.com, cpgs@samsung.com,
	pintu_agarwal@yahoo.com, pintu.k@outlook.com,
	vishnu.ps@samsung.com, rohit.kr@samsung.com
Subject: Re: [PATCH 1/1] mm: vmstat: introducing vm counter for slowpath
Date: Fri, 7 Aug 2015 09:44:22 +0200	[thread overview]
Message-ID: <20150807074422.GE26566@dhcp22.suse.cz> (raw)
In-Reply-To: <1438931334-25894-1-git-send-email-pintu.k@samsung.com>

On Fri 07-08-15 12:38:54, Pintu Kumar wrote:
> This patch add new counter slowpath_entered in /proc/vmstat to
> track how many times the system entered into slowpath after
> first allocation attempt is failed.

This is too lowlevel to be exported in the regular user visible
interface IMO.

> This is useful to know the rate of allocation success within
> the slowpath.

What would be that information good for? Is a regular administrator
expected to consume this value or this is aimed more to kernel
developers? If the later then I think a trace point sounds like a better
interface.

> This patch is tested on ARM with 512MB RAM.
> A sample output is shown below after successful boot-up:
> shell> cat /proc/vmstat
> nr_free_pages 4712
> pgalloc_normal 1319432
> pgalloc_movable 0
> pageoutrun 379
> allocstall 0
> slowpath_entered 585
> compact_stall 0
> compact_fail 0
> compact_success 0
> 
> >From the above output we can see that the system entered
> slowpath 585 times.
> But the existing counter kswapd(pageoutrun), direct_reclaim(allocstall),
> direct_compact(compact_stall) does not tell this value.
> >From the above value, it clearly indicates that the system have
> entered slowpath 585 times. Out of which 379 times allocation passed
> through kswapd, without performing direct reclaim/compaction.
> That means the remaining 206 times the allocation would have succeeded
> using the alloc_pages_high_priority.
> 
> Signed-off-by: Pintu Kumar <pintu.k@samsung.com>
-- 
Michal Hocko
SUSE Labs

  reply	other threads:[~2015-08-07  7:44 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-07  7:08 Pintu Kumar
2015-08-07  7:44 ` Michal Hocko [this message]
2015-08-07 12:46   ` PINTU KUMAR
2015-08-07 14:30     ` Michal Hocko
2015-08-07 22:35     ` Andrew Morton
2015-08-10  9:45       ` PINTU KUMAR
2015-08-11 10:55         ` Michal Hocko
2015-08-12 14:52           ` PINTU KUMAR
2015-08-13  9:07             ` Michal Hocko
2015-08-07  7:50 ` Sergey Senozhatsky

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=20150807074422.GE26566@dhcp22.suse.cz \
    --to=mhocko@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=alexander.h.duyck@redhat.com \
    --cc=cl@linux.com \
    --cc=cpgs@samsung.com \
    --cc=dave@stgolabs.net \
    --cc=fengguang.wu@intel.com \
    --cc=hannes@cmpxchg.org \
    --cc=js1304@gmail.com \
    --cc=koct9i@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mgorman@suse.de \
    --cc=minchan@kernel.org \
    --cc=pintu.k@outlook.com \
    --cc=pintu.k@samsung.com \
    --cc=pintu_agarwal@yahoo.com \
    --cc=rohit.kr@samsung.com \
    --cc=sasha.levin@oracle.com \
    --cc=vbabka@suse.cz \
    --cc=vishnu.ps@samsung.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

all inboxes | Powered by JetHome®