From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758706AbXKAIDm (ORCPT ); Thu, 1 Nov 2007 04:03:42 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1755555AbXKAIDa (ORCPT ); Thu, 1 Nov 2007 04:03:30 -0400 Received: from smtp-out.google.com ([216.239.45.13]:60600 "EHLO smtp-out.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752404AbXKAID2 (ORCPT ); Thu, 1 Nov 2007 04:03:28 -0400 DomainKey-Signature: a=rsa-sha1; s=beta; d=google.com; c=nofws; q=dns; h=received:date:from:x-x-sender:to:cc:subject:in-reply-to: message-id:references:mime-version:content-type; b=Ta9TCAoop3czzQn+jFH4gwgVjDregaR8oGIxPFWeWGVTz289qFEsldM51AhqRsKxD 0DW3YJak4Clt6qzmj34pg== Date: Thu, 1 Nov 2007 01:03:18 -0700 (PDT) From: David Rientjes X-X-Sender: rientjes@chino.kir.corp.google.com To: Paul Jackson cc: Christoph Lameter , Lee.Schermerhorn@hp.com, linux-kernel@vger.kernel.org, ak@suse.de Subject: Re: [RFC] cpuset relative memory policies - second choice In-Reply-To: <20071031233352.959c32d0.pj@sgi.com> Message-ID: References: <20071031061729.18174.60384.sendpatchset@jackhammer.engr.sgi.com> <20071031131949.b91bf383.pj@sgi.com> <20071031214719.81f8293a.pj@sgi.com> <20071031233352.959c32d0.pj@sgi.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Wed, 31 Oct 2007, Paul Jackson wrote: > David R - is your use of the mbind and *_mempolicy system calls > via libnuma, or direct system calls? > I hope to be able to use libnuma exclusively once your fix is in place so that the interleaving behaves the way we want while attached to a changing cpuset. (And it would be preferable to not have to use a special version of it that is hacked to support the fix.) It's just simpler to use as an interface, but I wouldn't consider using the system calls directly an error. David