From: Arun Sharma <asharma@fb.com>
To: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Cc: Balbir Singh <bsingharora@gmail.com>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
akpm@linux-foundation.org
Subject: Re: [PATCH] mm: Enable MAP_UNINITIALIZED for archs with mmu
Date: Fri, 24 Feb 2012 11:26:51 -0800 [thread overview]
Message-ID: <4F47E47B.3000409@fb.com> (raw)
In-Reply-To: <20120224114748.720ee79a.kamezawa.hiroyu@jp.fujitsu.com>
On 2/23/12 6:47 PM, KAMEZAWA Hiroyuki wrote:
>>
>> In a distributed computing environment, a user submits a job to the
>> cluster job scheduler. The job might involve multiple related
>> executables and might involve multiple address spaces. But they're
>> performing one logical task, have a single resource limit enforced by a
>> cgroup.
>>
>> They don't have access to each other's VMAs, but if "accidentally" one
>> of them comes across an uninitialized page with data from another task,
>> it's not a violation of the security model.
>>
> How do you handle shared resouce, file-cache ?
>
From a security perspective or a resource limit perspective?
Security: all processes in the cgroup run with the same uid and have the
same access to the filesystem. Multiple address spaces in a cgroup can
be thought of as an implementation detail.
Resource limit: We don't have strict enforcement right now. There is a
desire to include everything (file cache, slab memory) in the job's
memory resource limit.
-Arun
--
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>
prev parent reply other threads:[~2012-02-24 19:27 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-18 18:51 [PATCH] mm: Enable MAP_UNINITIALIZED for archs with mmu Arun Sharma
2012-01-19 2:42 ` KAMEZAWA Hiroyuki
2012-01-24 0:54 ` Arun Sharma
2012-01-24 3:07 ` KAMEZAWA Hiroyuki
2012-01-25 1:45 ` Arun Sharma
2012-02-22 0:34 ` Arun Sharma
2012-02-23 7:45 ` Balbir Singh
2012-02-23 18:42 ` Arun Sharma
2012-02-24 2:47 ` KAMEZAWA Hiroyuki
2012-02-24 14:51 ` Balbir Singh
2012-02-24 19:11 ` Arun Sharma
2012-02-25 4:13 ` Balbir Singh
2012-02-27 18:32 ` Arun Sharma
2012-02-24 19:26 ` Arun Sharma [this message]
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=4F47E47B.3000409@fb.com \
--to=asharma@fb.com \
--cc=akpm@linux-foundation.org \
--cc=bsingharora@gmail.com \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--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).