[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <whmqaksbwuksdobz2fomqi3pa7btf2ucjtr3i4bz3oglidz3n2@27zggp5udztd>
Date: Sun, 27 Oct 2024 18:59:13 -0700
From: Davidlohr Bueso <dave@...olabs.net>
To: "Christoph Lameter (Ampere)" <cl@...two.org>
Cc: Peter Zijlstra <peterz@...radead.org>, tglx@...utronix.de,
linux-kernel@...r.kernel.org, mingo@...hat.com, dvhart@...radead.org, andrealmeid@...lia.com,
Andrew Morton <akpm@...ux-foundation.org>, urezki@...il.com, hch@...radead.org, lstoakes@...il.com,
Arnd Bergmann <arnd@...db.de>, linux-api@...r.kernel.org, linux-mm@...ck.org,
linux-arch@...r.kernel.org, malteskarupke@....de, llong@...hat.com
Subject: Re: [PATCH 2/6] futex: Implement FUTEX2_NUMA
On Fri, 25 Oct 2024, Christoph Lameter (Ampere) wrote:\n
>Would it be possible to follow the NUMA memory policy set up for a task
>when making these decisions? We may not need a separate FUTEX2_NUMA
>option. There are supportive functions in mm/mempolicy.c that will yield
>a node for the futex logic to use.
With numa-awareness, when would lookups ever want to be anywhere but
local? mempolicy is about allocations, futexes are not that.
Powered by blists - more mailing lists