[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <e3d978ce-146c-36a5-3ae3-bddb80440203@gentwo.org>
Date: Mon, 7 Oct 2024 09:19:18 -0700 (PDT)
From: "Christoph Lameter (Ampere)" <cl@...two.org>
To: Hyeonggon Yoo <42.hyeyoo@...il.com>
cc: Vlastimil Babka <vbabka@...e.cz>, Pekka Enberg <penberg@...nel.org>,
David Rientjes <rientjes@...gle.com>, Joonsoo Kim <iamjoonsoo.kim@....com>,
Andrew Morton <akpm@...ux-foundation.org>,
Roman Gushchin <roman.gushchin@...ux.dev>, Yang Shi <shy828301@...il.com>,
linux-mm@...ck.org, linux-kernel@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org,
Huang Shijie <shijie@...amperecomputing.com>
Subject: Re: [PATCH v3] SLUB: Add support for per object memory policies
On Sun, 6 Oct 2024, Hyeonggon Yoo wrote:
> > + */
> > + if (mpol->mode != MPOL_BIND || !slab ||
> > + !node_isset(slab_nid(slab), mpol->nodes))
> > +
> > + node = mempolicy_slab_node();
> > + }
>
> Is it intentional to allow the local node only (via
> mempolicy_slab_node()) in interrupt contexts?
Yes that is the general approach since the task context is generally not
valid for the interrupt which is usually from a device that is not task
specific.
Powered by blists - more mailing lists