From: "Michael Kerrisk" <mtk-manpages@gmx.net>
To: Christoph Lameter <clameter@sgi.com>
Cc: akpm@osdl.org, ak@suse.de, linux-mm@kvack.org, michael.kerrisk@gmx.net
Subject: Re: Inconsistent capabilites associated with MPOL_MOVE_ALL
Date: Wed, 15 Mar 2006 01:40:56 +0100 (MET) [thread overview]
Message-ID: <32623.1142383256@www015.gmx.net> (raw)
In-Reply-To: <Pine.LNX.4.64.0603141632210.23051@schroedinger.engr.sgi.com>
> --- Ursprungliche Nachricht ---
> Von: Christoph Lameter <clameter@sgi.com>
> An: akpm@osdl.org
> Kopie: Michael Kerrisk <mtk-manpages@gmx.net>, ak@suse.de,
> linux-mm@kvack.org, michael.kerrisk@gmx.net
> Betreff: Re: Inconsistent capabilites associated with MPOL_MOVE_ALL
> Datum: Tue, 14 Mar 2006 16:33:29 -0800 (PST)
>
> On Wed, 15 Mar 2006, Michael Kerrisk wrote:
>
> > It seems to me that setting scheduling policy and
> > priorities is also the kind of thing that might be performed
> > in apps that also use the NUMA API, so it would seem consistent
> > to use CAP_SYS_NICE for NUMA also.
>
> Use CAP_SYS_NICE for controlling migration permissions.
Ahhh -- the sweet smell of consistency...
Thanks!
Michael
--
Michael Kerrisk
maintainer of Linux man pages Sections 2, 3, 4, 5, and 7
Want to help with man page maintenance?
Grab the latest tarball at
ftp://ftp.win.tue.nl/pub/linux-local/manpages/,
read the HOWTOHELP file and grep the source
files for 'FIXME'.
--
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:[~2006-03-15 0:40 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-03 16:58 numa_maps update Christoph Lameter
2006-03-04 9:07 ` Andrew Morton
2006-03-04 4:59 ` Andi Kleen
2006-03-04 20:08 ` Christoph Lameter
2006-03-04 20:26 ` Andrew Morton
2006-03-06 16:19 ` Christoph Lameter
2006-03-06 17:37 ` Christoph Lameter
2006-03-15 0:01 ` Inconsistent capabilites associated with MPOL_MOVE_ALL Michael Kerrisk
2006-03-15 0:09 ` Christoph Lameter
2006-03-15 0:25 ` Michael Kerrisk
2006-03-15 0:33 ` Christoph Lameter
2006-03-15 0:40 ` Michael Kerrisk [this message]
2006-03-15 0:41 ` Andrew Morton
2006-03-15 0:53 ` Christoph Lameter
2006-03-15 1:01 ` Andrew Morton
2006-03-15 1:07 ` Michael Kerrisk
2006-03-15 1:12 ` Michael Kerrisk
2006-03-15 1:16 ` Christoph Lameter
2006-03-15 1:08 ` Christoph Lameter
2006-03-15 0:59 ` Michael Kerrisk
2006-03-15 1:16 ` Andrew Morton
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=32623.1142383256@www015.gmx.net \
--to=mtk-manpages@gmx.net \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--cc=clameter@sgi.com \
--cc=linux-mm@kvack.org \
--cc=michael.kerrisk@gmx.net \
/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