From: "Christoph Lameter (Ampere)" <cl@gentwo.org>
To: Hyeonggon Yoo <42.hyeyoo@gmail.com>
Cc: Vlastimil Babka <vbabka@suse.cz>,
Pekka Enberg <penberg@kernel.org>,
David Rientjes <rientjes@google.com>,
Joonsoo Kim <iamjoonsoo.kim@lge.com>,
Andrew Morton <akpm@linux-foundation.org>,
Roman Gushchin <roman.gushchin@linux.dev>,
Yang Shi <shy828301@gmail.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Huang Shijie <shijie@os.amperecomputing.com>
Subject: Re: [PATCH v3] SLUB: Add support for per object memory policies
Date: Mon, 7 Oct 2024 09:19:18 -0700 (PDT) [thread overview]
Message-ID: <e3d978ce-146c-36a5-3ae3-bddb80440203@gentwo.org> (raw)
In-Reply-To: <CAB=+i9T8cOLQt4YprvUghwWZx1nOaiQ-0vV1N1zOOHWAFXza0Q@mail.gmail.com>
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.
next prev parent reply other threads:[~2024-10-07 16:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-01 19:08 Christoph Lameter via B4 Relay
2024-10-02 10:32 ` Vlastimil Babka
2024-10-02 17:52 ` Christoph Lameter (Ampere)
2024-10-03 9:51 ` Vlastimil Babka
2024-10-06 14:37 ` Hyeonggon Yoo
2024-10-07 16:19 ` Christoph Lameter (Ampere) [this message]
2024-10-08 9:48 ` Vlastimil Babka
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=e3d978ce-146c-36a5-3ae3-bddb80440203@gentwo.org \
--to=cl@gentwo.org \
--cc=42.hyeyoo@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=iamjoonsoo.kim@lge.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=penberg@kernel.org \
--cc=rientjes@google.com \
--cc=roman.gushchin@linux.dev \
--cc=shijie@os.amperecomputing.com \
--cc=shy828301@gmail.com \
--cc=vbabka@suse.cz \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox