MIME-version: 1.0
Content-transfer-encoding: 7BIT
Content-type: text/plain; charset=us-ascii
From: Stefan Lankes <lankes@lfbs.rwth-aachen.de>
To: "'Brice Goglin'" <Brice.Goglin@inria.fr>
Cc: "'Andi Kleen'" <andi@firstfloor.org>, linux-kernel@vger.kernel.org,
       Lee.Schermerhorn@hp.com, linux-numa@vger.kernel.org,
       Boris Bierbaum <boris@lfbs.rwth-aachen.de>
References: <000c01c9d212$4c244720$e46cd560$@rwth-aachen.de>
 <87zldjn597.fsf@basil.nowhere.org>
 <000001c9eac4$cb8b6690$62a233b0$@rwth-aachen.de>
 <20090612103251.GJ25568@one.firstfloor.org>
 <004001c9eb53$71991300$54cb3900$@rwth-aachen.de> <4A324A4E.1060405@inria.fr>
In-reply-to: 
Subject: RE: [RFC PATCH 0/4]: affinity-on-next-touch
Date: Fri, 12 Jun 2009 15:48:36 +0200
Organization: Chair for Operating Systems, RWTH Aachen University
Message-id: <004601c9eb64$7c23fcc0$746bf640$@rwth-aachen.de>
Thread-index: AcnrWXHDyy/c1RqIQvS1JLHUD9yOpQAAVQdAAAItwQA=
Content-language: de
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 714
Lines: 19

> >
> 
> MPOL_MF_LAZY is used as flag and does not specify a new policy.
> Therefore, MPOL_MF_LAZY isn't stored in a VMA. The flag is only used to
> detect that the system call mbind has to unmap these pages.
> 

In one of my previous e-mails, I wrote that Lee use the normal NUMA memory
policies. This statement was unclear. Lee's patches define no new memory
policy. He adds only a new flag. The using of mbind looks for me smarter as
the using of madvise. 

Stefan

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/