[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAHk-=wiR+dTAw7qRGRQ80B4oUZEithHd2J4ZfNjc5eGqY1mWwA@mail.gmail.com>
Date: Mon, 25 Apr 2022 14:42:34 -0700
From: Linus Torvalds <torvalds@...ux-foundation.org>
To: Andrew Morton <akpm@...ux-foundation.org>
Cc: Sudip Mukherjee <sudipm.mukherjee@...il.com>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Linux-MM <linux-mm@...ck.org>, Song Liu <song@...nel.org>
Subject: Re: Linux 5.18-rc4
On Mon, Apr 25, 2022 at 2:27 PM Andrew Morton <akpm@...ux-foundation.org> wrote:
>
> From: Andrew Morton <akpm@...ux-foundation.org>
> Subject: mm/nommu.c: provide vmalloc_huge() for CONFIG_MMU=n
Note, should already be fixed differently (with an alias) by
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=0fc74d820a012550be006ba82dd8f1e3fe6fa9f7
although when I looked at the random collection of vmalloc things it
did make me go "hmm".
It might be a better long-term idea to only implement the very generic
low-level function in mm/vmalloc.c and mm/nommu.c (ie the
__vmalloc_node_range() function) and then move all the random wrapper
functions into mm/util.c.
Because right now we effectively duplicate all those wrapper
functions, which is kind of ugly.
Linus
Powered by blists - more mailing lists