From: "Kirill A. Shutemov" <kirill@shutemov.name>
To: Federico Reghenzani <federico.reghenzani@polimi.it>
Cc: linux-mm@kvack.org
Subject: Re: mlockall() with pid parameter
Date: Wed, 7 Dec 2016 21:42:36 +0300 [thread overview]
Message-ID: <20161207184236.GA5593@node.shutemov.name> (raw)
In-Reply-To: <CACKey4xEaMJ8qQyT7H5jQSxEBrxxuopg2a_AiMFJLeTTA+M9Lg@mail.gmail.com>
On Wed, Dec 07, 2016 at 04:39:13PM +0100, 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.
For raising rlimits, you don't really need full root, only
CAP_SYS_RESOURCES (I'm not sure if it's any safer than full root in
practice).
It gives one other possible approach: set the capability for the binary.
Real-time proceses is already somewhat priviledged, right?
I mean CAP_SYS_NICE.
--
Kirill A. Shutemov
--
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>
prev parent reply other threads:[~2016-12-07 18:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-07 15:39 mlockall() with pid parameter 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
2016-12-07 18:42 ` Kirill A. Shutemov [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=20161207184236.GA5593@node.shutemov.name \
--to=kirill@shutemov.name \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.