From: Prakash Sangappa <prakash.sangappa@oracle.com>
To: "Enrico Weigelt, metux IT consult" <lkml@metux.net>,
Jann Horn <jannh@google.com>
Cc: kernel list <linux-kernel@vger.kernel.org>,
Linux API <linux-api@vger.kernel.org>,
"Eric W. Biederman" <ebiederm@xmission.com>,
Thomas Gleixner <tglx@linutronix.de>,
Peter Zijlstra <peterz@infradead.org>,
"Serge E. Hallyn" <serge@hallyn.com>,
Christian Brauner <christian@brauner.io>
Subject: Re: [RESEND RFC PATCH 0/1] CAP_SYS_NICE inside user namespace
Date: Thu, 21 Nov 2019 17:54:13 -0800 [thread overview]
Message-ID: <4593138d-421e-5770-6dd5-e31f103911c5@oracle.com> (raw)
In-Reply-To: <c7949242-385f-3256-b290-87640acd0577@metux.net>
On 11/21/19 10:33 AM, Enrico Weigelt, metux IT consult wrote:
> On 18.11.19 21:34, Prakash Sangappa wrote:
>
>> It is more the latter. Admin should be able to explicitly decide that container A
>> workload is to be given priority over other containers.
> I guess, you're talking about the host's admin, correct ?
Yes, Specifically host's admin decides which container gets the
privilege to increase priority of processes inside that container.
>
> Shouldn't this already be possibly by tweaking the container's cgroups ?
Don't think so. The use case is that admin/user inside the container
needs to be able to increase the priority of some the critical processes
running in the container.
>
>
> --mtx
>
prev parent reply other threads:[~2019-11-22 1:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-18 17:01 [RESEND RFC PATCH 0/1] CAP_SYS_NICE inside user namespace Prakash Sangappa
2019-11-18 17:01 ` [RESEND RFC PATCH 1/1] Selectively allow CAP_SYS_NICE capability inside user namespaces Prakash Sangappa
2019-11-18 19:30 ` Jann Horn
2019-11-19 0:46 ` prakash.sangappa
2019-11-21 21:27 ` Eric W. Biederman
2019-11-22 1:45 ` Prakash Sangappa
2020-01-08 21:23 ` prakash.sangappa
2019-11-18 19:36 ` [RESEND RFC PATCH 0/1] CAP_SYS_NICE inside user namespace Jann Horn
2019-11-18 20:34 ` Prakash Sangappa
2019-11-21 18:33 ` Enrico Weigelt, metux IT consult
2019-11-22 1:54 ` Prakash Sangappa [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=4593138d-421e-5770-6dd5-e31f103911c5@oracle.com \
--to=prakash.sangappa@oracle.com \
--cc=christian@brauner.io \
--cc=ebiederm@xmission.com \
--cc=jannh@google.com \
--cc=linux-api@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkml@metux.net \
--cc=peterz@infradead.org \
--cc=serge@hallyn.com \
--cc=tglx@linutronix.de \
/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).