From: Michal Hocko <mhocko@kernel.org>
To: Li RongQing <lirongqing@baidu.com>
Cc: akpm@linux-foundation.org, kirill.shutemov@linux.intel.com,
jglisse@redhat.com, minchan@kernel.org, linux-mm@kvack.org
Subject: Re: [PATCH] mm: limit a process RSS
Date: Tue, 3 Apr 2018 09:36:57 +0200 [thread overview]
Message-ID: <20180403073657.GA5501@dhcp22.suse.cz> (raw)
In-Reply-To: <1522655119-6317-1-git-send-email-lirongqing@baidu.com>
On Mon 02-04-18 15:45:19, Li RongQing wrote:
> we cannot limit a process RSS although there is ulimit -m,
> not sure why and when ulimit -m is not working, make it work
Could you be more specific about why do you need this functionality?
The RSS limit has never been implemented AFAIK and the main reason is
that the semantic is quite weak to be useful (e.g. the shared memory
accounting, resident memory that is not mapped etc.).
We have memory cgroup controller as an alternative.
--
Michal Hocko
SUSE Labs
next parent reply other threads:[~2018-04-03 7:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1522655119-6317-1-git-send-email-lirongqing@baidu.com>
2018-04-03 7:36 ` Michal Hocko [this message]
2018-04-03 8:20 ` 答复: " Li,Rongqing
2018-04-03 8:29 ` Michal Hocko
2018-03-30 5:11 Li RongQing
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=20180403073657.GA5501@dhcp22.suse.cz \
--to=mhocko@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=jglisse@redhat.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-mm@kvack.org \
--cc=lirongqing@baidu.com \
--cc=minchan@kernel.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