From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Thu, 10 Oct 2002 15:10:14 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Thu, 10 Oct 2002 15:10:13 -0400 Received: from e35.co.us.ibm.com ([32.97.110.133]:2300 "EHLO e35.co.us.ibm.com") by vger.kernel.org with ESMTP id ; Thu, 10 Oct 2002 15:09:32 -0400 Message-ID: <3DA5D052.4020908@us.ibm.com> Date: Thu, 10 Oct 2002 12:09:06 -0700 From: Matthew Dobson Reply-To: colpatch@us.ibm.com Organization: IBM LTC User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.0) Gecko/20020607 X-Accept-Language: en-us, en MIME-Version: 1.0 To: William Lee Irwin III CC: Alan Cox , Arjan van de Ven , Linux Kernel Mailing List , linux-mm@kvack.org, LSE , Andrew Morton , Martin Bligh , Michael Hohnbaum Subject: Re: [rfc][patch] Memory Binding API v0.3 2.5.41 References: <3DA4D3E4.6080401@us.ibm.com> <1034244381.3629.8.camel@localhost.localdomain> <1034248971.2044.118.camel@irongate.swansea.linux.org.uk> <20021010112844.GW12432@holomorphy.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org William Lee Irwin III wrote: > At some point in the past, Matthew Dobson wrote: > >>>>+asmlinkage long sys_mem_setbinding(pid_t pid, unsigned long memblks, >>>>+ unsigned int behavior) >>> > > On Thu, 2002-10-10 at 11:06, Arjan van de Ven wrote: > >>>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?) >> > > On Thu, Oct 10, 2002 at 12:22:51PM +0100, Alan Cox wrote: > >>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 > Seconded wrt. memblk bitmask interface. Glad to have your support! :) > Also, I've already privately replied with some of my stylistic concerns, > including things like the separability of the for_each_in_zonelist() > cleanup bundled into the patch and a typedef or so. Some very good points in your email. Most (if not all) will be incorporated in v0.4 (later today or tomorrow). Cheers! -Matt