From: Vlastimil Babka <vbabka@suse.cz>
To: Federico Reghenzani <federico.reghenzani@polimi.it>, linux-mm@kvack.org
Subject: Re: mlockall() with pid parameter
Date: Wed, 7 Dec 2016 17:21:38 +0100 [thread overview]
Message-ID: <52a0d9c3-5c9a-d207-4cbc-a6df27ba6a9c@suse.cz> (raw)
In-Reply-To: <CACKey4xEaMJ8qQyT7H5jQSxEBrxxuopg2a_AiMFJLeTTA+M9Lg@mail.gmail.com>
On 12/07/2016 04:39 PM, Federico Reghenzani wrote:
> Hello,
>
> I'm working on Real-Time applications in Linux. `mlockall()` is a
> typical syscall used in RT processes in order to avoid page faults.
> However, the use of this syscall is strongly limited by ulimits, so
> basically all RT processes that want to call `mlockall()` have to be
> executed with root privileges.
Is it not possible to change the ulimits with e.g. prlimit?
> 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);
>
> I checked the source code and it seems to me quite easy to add this
> syscall variant.
>
> I'm writing here to have a feedback before starting to edit the code. Do
> you think that this is a good approach?
>
>
> Thank you,
> Federico
>
> --
> *Federico Reghenzani*
> PhD Candidate
> Politecnico di Milano
> Dipartimento di Elettronica, Informazione e Bioingegneria
>
--
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 16:21 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 [this message]
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
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=52a0d9c3-5c9a-d207-4cbc-a6df27ba6a9c@suse.cz \
--to=vbabka@suse.cz \
--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