From: Arjan van de Ven <arjanv@fenrus.demon.nl>
To: colpatch@us.ibm.com
Cc: linux-kernel <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:06:20 +0200 [thread overview]
Message-ID: <1034244381.3629.8.camel@localhost.localdomain> (raw)
In-Reply-To: <3DA4D3E4.6080401@us.ibm.com>
[-- Attachment #1: Type: text/plain, Size: 820 bytes --]
> +/**
> + * 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?)
I'd much rather see the VM have an arch-specified "cost" for getting
memory from not-the-prefered zones than exposing all this stuff to
userspace and depending on userspace to do the right thing.... it's the
kernel's task to abstract the low level details of the hardware after
all.
Greetings,
Arjan van de Ven
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2002-10-10 10:06 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 [this message]
2002-10-10 11:22 ` Alan Cox
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=1034244381.3629.8.camel@localhost.localdomain \
--to=arjanv@fenrus.demon.nl \
--cc=akpm@zip.com.au \
--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