All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Stancek <jstancek@redhat.com>
To: manjeet p <manjeet.p@samsung.com>
Cc: AJEET YADAV <ajeet.y@samsung.com>,
	ltp-list@lists.sourceforge.net,
	PANKAJ MISHRA <pankaj.m@samsung.com>
Subject: Re: [LTP] Regarding memcg control  testcase (mem_process.c)
Date: Wed, 29 Jul 2015 02:48:43 -0400 (EDT)	[thread overview]
Message-ID: <1961298991.213904.1438152523150.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <1590056734.149151438142095446.JavaMail.weblogic@epmlwas07a>





----- Original Message -----
> From: "Manjeet Pawar" <manjeet.p@samsung.com>
> To: "Jan Stancek" <jstancek@redhat.com>, ltp-list@lists.sourceforge.net
> Cc: "AJEET YADAV" <ajeet.y@samsung.com>, "PANKAJ MISHRA" <pankaj.m@samsung.com>
> Sent: Wednesday, 29 July, 2015 5:54:55 AM
> Subject: Re: Re: [LTP]  Regarding memcg control  testcase (mem_process.c)
> 
> Hello Jan,
> After doing analysis, I found that When memory hog process (mem_process)
> tries to mmap double the memory of the cgroup limit which is 4096 . I am
> getting OOM in that situation and send kill signal to process (which is
> expected behaviour) . But it could not kill the process and
>  it sets the process state to uninterrupted sleep state.
> 
> To get this OOM , i need to change oom_adj value of the process '208' from
> -17 to -16. If i dont do this, I dont get OOM and process always stuck at
> mmap and try to allocate 8192 Bytes of memory.

That explains it, -17 means OOM is disabled:
#define OOM_DISABLE (-17)

> logs:-
> [2-74.5749] Memory cgroup out of memory: Kill process 208 (mem_process) score
> 147000 or sacrifice child
> [2-74.5840] Killed process 208 (mem_process) total-vm:2704kB, anon-rss:80kB,
> file-rss:484kB
> by mmap is -1237753856
> Warning: bad syntax, perhaps a bogus '-'? See /usr/share/doc/procps-3.2.8/FAQ
> root       208 39.6  0.0   2704   564 ?        D    00:01   0:02 mem_process
> -m 8192  // D - means uninterrupted sleep
> root       215  0.0  0.0   2412   584 ?        S    00:01   0:00 grep -r 208

No idea why it's getting stuck though. I'd try with oom_adj == 0. If that makes
no difference, /proc/<pid>/stack might give some additional clues.

Do you see similar behaviour with other OOM testcases?

Regards,
Jan

> 
> I am using 3.10.84 kernel. LTP is of latest  version (ltp-full-20150420)
> 
> Regards
> Manjeet
> 
> ------- Original Message -------
> Sender : Jan Stancek<jstancek@redhat.com>
> Date : Jul 27, 2015 17:32 (GMT+09:00)
> Title : Re: [LTP] Regarding memcg control testcase (mem_process.c)
> 
> 
> 
> 

------------------------------------------------------------------------------
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list

  reply	other threads:[~2015-07-29  6:48 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-29  3:54 [LTP] Regarding memcg control testcase (mem_process.c) Manjeet Pawar
2015-07-29  6:48 ` Jan Stancek [this message]
  -- strict thread matches above, loose matches on Subject: below --
2015-07-29  9:10 Manjeet Pawar
2015-07-27  8:12 Manjeet Pawar
2015-07-27  8:32 ` Jan Stancek
2015-07-24  4:07 Manjeet Pawar
2015-07-26 11:28 ` Jan Stancek

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=1961298991.213904.1438152523150.JavaMail.zimbra@redhat.com \
    --to=jstancek@redhat.com \
    --cc=ajeet.y@samsung.com \
    --cc=ltp-list@lists.sourceforge.net \
    --cc=manjeet.p@samsung.com \
    --cc=pankaj.m@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.