From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Arjan van de Ven <arjanv@fenrus.demon.nl>
Cc: colpatch@us.ibm.com,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-mm@kvack.org, LSE <lse-tech@lists.sourceforge.net>,
Andrew Morton <akpm@zip.com.au>,
Martin Bligh <mjbligh@us.ibm.com>,
Michael Hohnbaum <hohnbaum@us.ibm.com>
Subject: Re: [rfc][patch] Memory Binding API v0.3 2.5.41
Date: 10 Oct 2002 12:22:51 +0100 [thread overview]
Message-ID: <1034248971.2044.118.camel@irongate.swansea.linux.org.uk> (raw)
In-Reply-To: <1034244381.3629.8.camel@localhost.localdomain>
On Thu, 2002-10-10 at 11:06, Arjan van de Ven wrote:
>
> > +/**
> > + * sys_mem_setbinding - set the memory binding of a process
> > + * @pid: pid of the process
> > + * @memblks: new bitmask of memory blocks
> > + * @behavior: new behavior
> > + */
> > +asmlinkage long sys_mem_setbinding(pid_t pid, unsigned long memblks,
> > + unsigned int behavior)
> > +{
>
> Do you really think exposing low level internals as memory layout / zone
> split up to userspace is a good idea ? (and worth it given that the VM
> already has a cpu locality preference?)
At least in the embedded world that level is a good idea. I'm not sure
about the syscall interface. An "unsigned long" mask of blocks sounds
like a good way to ensure a broken syscall in the future
--
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/
next prev parent reply other threads:[~2002-10-10 11:22 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-10 1:12 Matthew Dobson
2002-10-10 3:05 ` Andrew Morton
2002-10-10 18:29 ` Matthew Dobson
2002-10-10 4:06 ` Martin J. Bligh
2002-10-10 18:43 ` Matthew Dobson
2002-10-10 9:00 ` Arjan van de Ven
2002-10-10 18:55 ` Matthew Dobson
2002-10-10 10:06 ` Arjan van de Ven
2002-10-10 11:22 ` Alan Cox [this message]
2002-10-10 11:28 ` William Lee Irwin III
2002-10-10 19:09 ` Matthew Dobson
2002-10-10 19:06 ` Matthew Dobson
2002-10-10 19:01 ` Matthew Dobson
2002-10-13 22:22 ` Eric W. Biederman
2002-10-15 0:14 ` Matthew Dobson
2002-10-15 0:20 ` Martin J. Bligh
2002-10-15 0:38 ` Matthew Dobson
2002-10-15 0:43 ` Martin J. Bligh
2002-10-15 0:51 ` Matthew Dobson
2002-10-15 0:58 ` William Lee Irwin III
2002-10-15 0:55 ` [Lse-tech] " john stultz
2002-10-15 1:08 ` Martin J. Bligh
2002-10-15 1:20 ` William Lee Irwin III
2002-10-15 1:29 ` Martin J. Bligh
2002-10-15 1:40 ` William Lee Irwin III
2002-10-15 1:57 ` William Lee Irwin III
2002-10-15 1:08 ` William Lee Irwin III
2002-10-15 1:16 ` Martin J. Bligh
2002-10-15 17:21 ` Eric W. Biederman
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=1034248971.2044.118.camel@irongate.swansea.linux.org.uk \
--to=alan@lxorguk.ukuu.org.uk \
--cc=akpm@zip.com.au \
--cc=arjanv@fenrus.demon.nl \
--cc=colpatch@us.ibm.com \
--cc=hohnbaum@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lse-tech@lists.sourceforge.net \
--cc=mjbligh@us.ibm.com \
/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