From: Dave Hansen <dave.hansen@intel.com>
To: Federico Reghenzani <federico.reghenzani@polimi.it>,
linux-mm@kvack.org, Vlastimil Babka <VBabka@suse.com>
Subject: Re: mlockall() with pid parameter
Date: Wed, 7 Dec 2016 09:40:04 -0800 [thread overview]
Message-ID: <4664bc3f-67b8-af11-3f98-a7d480996f5f@intel.com> (raw)
In-Reply-To: <CACKey4xEaMJ8qQyT7H5jQSxEBrxxuopg2a_AiMFJLeTTA+M9Lg@mail.gmail.com>
On 12/07/2016 07:39 AM, Federico Reghenzani wrote:
> What I would like to have is a syscall that accept a "pid", so a process
> spawned by root would be able to enforce the memory locking to other
> non-root processes. The prototypes would be:
>
> int mlockall(int flags, pid_t pid);
> int munlockall(pid_t pid);
The prototypes don't really tell enough of the story to give you good
feedback. For instance, whose rlimit do these count against? Are all
the MCL_CURRENT/FUTURE/FAULT flags supported?
I think you need to start implementing something to actually see how
ugly this gets in practice.
--
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>
next prev parent reply other threads:[~2016-12-07 17:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-07 15:39 Federico Reghenzani
2016-12-07 16:21 ` Vlastimil Babka
2016-12-07 16:33 ` Federico Reghenzani
2016-12-07 20:01 ` Vlastimil Babka
2016-12-08 12:58 ` Federico Reghenzani
2016-12-09 15:36 ` Federico Reghenzani
2016-12-07 17:40 ` Dave Hansen [this message]
2016-12-07 18:42 ` Kirill A. Shutemov
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=4664bc3f-67b8-af11-3f98-a7d480996f5f@intel.com \
--to=dave.hansen@intel.com \
--cc=VBabka@suse.com \
--cc=federico.reghenzani@polimi.it \
--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