All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anshuman Khandual <khandual@linux.vnet.ibm.com>
To: Pintu Kumar <pintu.k@samsung.com>,
	akpm@linux-foundation.org, minchan@kernel.org, dave@stgolabs.net,
	mhocko@suse.cz, koct9i@gmail.com, rientjes@google.com,
	hannes@cmpxchg.org, penguin-kernel@i-love.sakura.ne.jp,
	bywxiaobai@163.com, mgorman@suse.de, vbabka@suse.cz,
	js1304@gmail.com, kirill.shutemov@linux.intel.com,
	alexander.h.duyck@redhat.com, sasha.levin@oracle.com,
	cl@linux.com, fengguang.wu@intel.com,
	linux-kernel@vger.kernel.org, linux-mm@kvack.org
Cc: cpgs@samsung.com, pintu_agarwal@yahoo.com, pintu.ping@gmail.com,
	vishnu.ps@samsung.com, rohit.kr@samsung.com,
	c.rajkumar@samsung.com, sreenathd@samsung.com
Subject: Re: [PATCH 1/1] mm: vmstat: Add OOM kill count in vmstat counter
Date: Thu, 01 Oct 2015 18:59:38 +0530	[thread overview]
Message-ID: <560D3542.6060903@linux.vnet.ibm.com> (raw)
In-Reply-To: <1443696523-27262-1-git-send-email-pintu.k@samsung.com>

On 10/01/2015 04:18 PM, Pintu Kumar wrote:
> This patch maintains number of oom calls and number of oom kill
> count in /proc/vmstat.
> It is helpful during sluggish, aging or long duration tests.
> Currently if the OOM happens, it can be only seen in kernel ring buffer.
> But during long duration tests, all the dmesg and /var/log/messages* could
> be overwritten.
> So, just like other counters, the oom can also be maintained in
> /proc/vmstat.
> It can be also seen if all logs are disabled in kernel.

Makes sense.

> 
> A snapshot of the result of over night test is shown below:
> $ cat /proc/vmstat
> oom_stall 610
> oom_kill_count 1763
> 
> Here, oom_stall indicates that there are 610 times, kernel entered into OOM
> cases. However, there were around 1763 oom killing happens.
> The OOM is bad for the any system. So, this counter can help the developer
> in tuning the memory requirement at least during initial bringup.

Can you please fix the formatting of the commit message above ?

> 
> Signed-off-by: Pintu Kumar <pintu.k@samsung.com>
> ---
>  include/linux/vm_event_item.h |    2 ++
>  mm/oom_kill.c                 |    2 ++
>  mm/page_alloc.c               |    2 +-
>  mm/vmstat.c                   |    2 ++
>  4 files changed, 7 insertions(+), 1 deletion(-)
> 
> diff --git a/include/linux/vm_event_item.h b/include/linux/vm_event_item.h
> index 2b1cef8..ade0851 100644
> --- a/include/linux/vm_event_item.h
> +++ b/include/linux/vm_event_item.h
> @@ -57,6 +57,8 @@ enum vm_event_item { PGPGIN, PGPGOUT, PSWPIN, PSWPOUT,
>  #ifdef CONFIG_HUGETLB_PAGE
>  		HTLB_BUDDY_PGALLOC, HTLB_BUDDY_PGALLOC_FAIL,
>  #endif
> +		OOM_STALL,
> +		OOM_KILL_COUNT,

Removing the COUNT will be better and in sync with others.

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

WARNING: multiple messages have this Message-ID (diff)
From: Anshuman Khandual <khandual@linux.vnet.ibm.com>
To: Pintu Kumar <pintu.k@samsung.com>,
	akpm@linux-foundation.org, minchan@kernel.org, dave@stgolabs.net,
	mhocko@suse.cz, koct9i@gmail.com, rientjes@google.com,
	hannes@cmpxchg.org, penguin-kernel@i-love.sakura.ne.jp,
	bywxiaobai@163.com, mgorman@suse.de, vbabka@suse.cz,
	js1304@gmail.com, kirill.shutemov@linux.intel.com,
	alexander.h.duyck@redhat.com, sasha.levin@oracle.com,
	cl@linux.com, fengguang.wu@intel.com,
	linux-kernel@vger.kernel.org, linux-mm@kvack.org
Cc: cpgs@samsung.com, pintu_agarwal@yahoo.com, pintu.ping@gmail.com,
	vishnu.ps@samsung.com, rohit.kr@samsung.com,
	c.rajkumar@samsung.com, sreenathd@samsung.com
Subject: Re: [PATCH 1/1] mm: vmstat: Add OOM kill count in vmstat counter
Date: Thu, 01 Oct 2015 18:59:38 +0530	[thread overview]
Message-ID: <560D3542.6060903@linux.vnet.ibm.com> (raw)
In-Reply-To: <1443696523-27262-1-git-send-email-pintu.k@samsung.com>

On 10/01/2015 04:18 PM, Pintu Kumar wrote:
> This patch maintains number of oom calls and number of oom kill
> count in /proc/vmstat.
> It is helpful during sluggish, aging or long duration tests.
> Currently if the OOM happens, it can be only seen in kernel ring buffer.
> But during long duration tests, all the dmesg and /var/log/messages* could
> be overwritten.
> So, just like other counters, the oom can also be maintained in
> /proc/vmstat.
> It can be also seen if all logs are disabled in kernel.

Makes sense.

> 
> A snapshot of the result of over night test is shown below:
> $ cat /proc/vmstat
> oom_stall 610
> oom_kill_count 1763
> 
> Here, oom_stall indicates that there are 610 times, kernel entered into OOM
> cases. However, there were around 1763 oom killing happens.
> The OOM is bad for the any system. So, this counter can help the developer
> in tuning the memory requirement at least during initial bringup.

Can you please fix the formatting of the commit message above ?

> 
> Signed-off-by: Pintu Kumar <pintu.k@samsung.com>
> ---
>  include/linux/vm_event_item.h |    2 ++
>  mm/oom_kill.c                 |    2 ++
>  mm/page_alloc.c               |    2 +-
>  mm/vmstat.c                   |    2 ++
>  4 files changed, 7 insertions(+), 1 deletion(-)
> 
> diff --git a/include/linux/vm_event_item.h b/include/linux/vm_event_item.h
> index 2b1cef8..ade0851 100644
> --- a/include/linux/vm_event_item.h
> +++ b/include/linux/vm_event_item.h
> @@ -57,6 +57,8 @@ enum vm_event_item { PGPGIN, PGPGOUT, PSWPIN, PSWPOUT,
>  #ifdef CONFIG_HUGETLB_PAGE
>  		HTLB_BUDDY_PGALLOC, HTLB_BUDDY_PGALLOC_FAIL,
>  #endif
> +		OOM_STALL,
> +		OOM_KILL_COUNT,

Removing the COUNT will be better and in sync with others.


  reply	other threads:[~2015-10-01 13:30 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-01 10:48 [PATCH 1/1] mm: vmstat: Add OOM kill count in vmstat counter Pintu Kumar
2015-10-01 10:48 ` Pintu Kumar
2015-10-01 13:29 ` Anshuman Khandual [this message]
2015-10-01 13:29   ` Anshuman Khandual
2015-10-05  6:19   ` PINTU KUMAR
2015-10-05  6:19     ` PINTU KUMAR
2015-10-01 13:38 ` Michal Hocko
2015-10-01 13:38   ` Michal Hocko
2015-10-05  6:12   ` PINTU KUMAR
2015-10-05  6:12     ` PINTU KUMAR
2015-10-05 12:22     ` Michal Hocko
2015-10-05 12:22       ` Michal Hocko
2015-10-06  6:59       ` PINTU KUMAR
2015-10-06  6:59         ` PINTU KUMAR
2015-10-06 15:41         ` Michal Hocko
2015-10-06 15:41           ` Michal Hocko
2015-10-07 14:48           ` PINTU KUMAR
2015-10-07 14:48             ` PINTU KUMAR
2015-10-08 14:18             ` Michal Hocko
2015-10-08 14:18               ` Michal Hocko
2015-10-08 16:06               ` PINTU KUMAR
2015-10-08 16:06                 ` PINTU KUMAR
2015-10-08 16:30                 ` Michal Hocko
2015-10-08 16:30                   ` Michal Hocko
2015-10-09 12:59                   ` PINTU KUMAR
2015-10-09 12:59                     ` PINTU KUMAR
2015-10-12 13:33 ` [PATCH 1/1] mm: vmstat: Add OOM victims " Pintu Kumar
2015-10-12 13:33   ` Pintu Kumar
2015-10-12 14:28   ` [RESEND PATCH " Pintu Kumar
2015-10-12 14:28     ` Pintu Kumar
2015-10-14  3:05     ` David Rientjes
2015-10-14  3:05       ` David Rientjes
2015-10-14 13:41       ` PINTU KUMAR
2015-10-14 13:41         ` PINTU KUMAR
2015-10-14 22:04         ` David Rientjes
2015-10-14 22:04           ` David Rientjes
2015-10-15 14:35           ` PINTU KUMAR
2015-10-15 14:35             ` PINTU KUMAR
2015-10-12 14:44   ` [PATCH " PINTU KUMAR
2015-10-12 14:44     ` PINTU KUMAR

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=560D3542.6060903@linux.vnet.ibm.com \
    --to=khandual@linux.vnet.ibm.com \
    --cc=akpm@linux-foundation.org \
    --cc=alexander.h.duyck@redhat.com \
    --cc=bywxiaobai@163.com \
    --cc=c.rajkumar@samsung.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=kirill.shutemov@linux.intel.com \
    --cc=koct9i@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mgorman@suse.de \
    --cc=mhocko@suse.cz \
    --cc=minchan@kernel.org \
    --cc=penguin-kernel@i-love.sakura.ne.jp \
    --cc=pintu.k@samsung.com \
    --cc=pintu.ping@gmail.com \
    --cc=pintu_agarwal@yahoo.com \
    --cc=rientjes@google.com \
    --cc=rohit.kr@samsung.com \
    --cc=sasha.levin@oracle.com \
    --cc=sreenathd@samsung.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.