linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: "Michael Kerrisk" <michael.kerrisk@gmx.net>
To: Andrew Morton <akpm@osdl.org>
Cc: clameter@sgi.comclameter@sgi.com, ak@suse.de, linux-mm@kvack.org,
	michael.kerrisk@gmx.net, mtk-manpages@gmx.net
Subject: Re: Inconsistent capabilites associated with MPOL_MOVE_ALL
Date: Wed, 15 Mar 2006 14:12:00 +1300	[thread overview]
Message-ID: <441820B0.6719.396D781@michael.kerrisk.gmx.net> (raw)
In-Reply-To: <15030.1142384877@www015.gmx.net>

> > Von: Andrew Morton <akpm@osdl.org>
> > Christoph Lameter <clameter@sgi.com> wrote:
> > >
> > > On Tue, 14 Mar 2006, Andrew Morton wrote:
> > > 
> > > > Christoph Lameter <clameter@sgi.com> wrote:
> > > > >
> > > > > Use CAP_SYS_NICE for controlling migration permissions.
> > > > ahem.  Kind of eleventh-hour.  Are we really sure?
> > > 
> > > This may still get into 2.6.16???
> > 
> > Well it changes the userspace API.
> 
> No -- both of these changes affect interfaces
> that are only part of the unreleased 2.6.16. 
> (MPOL_MF_MOVE_ALL is new in 2.6.16.)

Replying to self...

Ooops sorry about the last -- I see that Christoph is changing stuff in 
addition to what I was proposing...  (But it makes sense to me, from a 
consistency point of view.)

Cheers,

Michael

--
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>

  reply	other threads:[~2006-03-15  1:12 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
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 [this message]
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=441820B0.6719.396D781@michael.kerrisk.gmx.net \
    --to=michael.kerrisk@gmx.net \
    --cc=akpm@osdl.org \
    --cc=clameter@sgi.comclameter \
    /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