[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20250313150814.075d1cd993a84005d4cd22c2@linux-foundation.org>
Date: Thu, 13 Mar 2025 15:08:14 -0700
From: Andrew Morton <akpm@...ux-foundation.org>
To: Sebastian Andrzej Siewior <bigeasy@...utronix.de>
Cc: linux-kernel@...r.kernel.org, André Almeida
<andrealmeid@...lia.com>, Darren Hart <dvhart@...radead.org>, Davidlohr
Bueso <dave@...olabs.net>, Ingo Molnar <mingo@...hat.com>, Juri Lelli
<juri.lelli@...hat.com>, Peter Zijlstra <peterz@...radead.org>, Thomas
Gleixner <tglx@...utronix.de>, Valentin Schneider <vschneid@...hat.com>,
Waiman Long <longman@...hat.com>, Uladzislau Rezki <urezki@...il.com>,
Christoph Hellwig <hch@...radead.org>, linux-mm@...ck.org, Christoph
Hellwig <hch@....de>
Subject: Re: [PATCH v10 19/21] mm: Add vmalloc_huge_node()
On Thu, 13 Mar 2025 08:59:24 +0100 Sebastian Andrzej Siewior <bigeasy@...utronix.de> wrote:
> >
> > I suppose we can now simplify vmalloc_huge_noprof() to use this:
> >
> > static inline void *vmalloc_huge_noprof(unsigned long size, gfp_t gfp_mask)
> > {
> > return vmalloc_huge_node_noprof(size, gfp_mask, NUMA_NO_NODE);
> > }
>
> Do you want me to stash this into this one or as a follow up?
That would be nice, if you think it makes sense. There is some
duplication here.
Powered by blists - more mailing lists