From: Michal Hocko <mhocko@suse.cz>
To: gaoqiang <gaoqiangscut@gmail.com>
Cc: cgroups@vger.kernel.org, linux-mm@kvack.org
Subject: Re: question about memsw of memory cgroup-subsystem
Date: Fri, 13 Apr 2012 16:49:54 +0200 [thread overview]
Message-ID: <20120413144954.GA9227@tiehlicka.suse.cz> (raw)
In-Reply-To: <op.wco7ekvhn27o5l@gaoqiang-d1.corp.qihoo.net>
[CC linux-mm]
Hi,
On Fri 13-04-12 18:00:10, gaoqiang wrote:
>
>
> I put a single process into a cgroup and set memory.limit_in_bytes
> to 100M,and memory.memsw.limit_in_bytes to 1G.
>
> howevery,the process was oom-killed before mem+swap hit 1G. I tried
> many times,and it was killed randomly when memory+swap
>
> exceed 100M but less than 1G. what is the matter ?
could you be more specific about your kernel version, workload and could
you provide us with GROUP/memory.stat snapshots taken during your test?
One reason for oom might be that you are hitting the hard limit (you
cannot get over even if memsw limit says more) and you cannot swap out
any pages (e.g. they are mlocked or under writeback).
--
Michal Hocko
SUSE Labs
SUSE LINUX s.r.o.
Lihovarska 1060/12
190 00 Praha 9
Czech Republic
--
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/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next parent reply other threads:[~2012-04-13 14:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <op.wco7ekvhn27o5l@gaoqiang-d1.corp.qihoo.net>
2012-04-13 14:49 ` Michal Hocko [this message]
2012-04-16 3:43 ` question about memsw of memory cgroup-subsystem gaoqiang
2012-04-16 14:26 ` Michal Hocko
2012-04-17 3:25 ` Sha Zhengju
2012-04-17 8:18 ` gaoqiang
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=20120413144954.GA9227@tiehlicka.suse.cz \
--to=mhocko@suse.cz \
--cc=cgroups@vger.kernel.org \
--cc=gaoqiangscut@gmail.com \
--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;
as well as URLs for NNTP newsgroup(s).