[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ZGZW0v3nRShO7r+Z@moria.home.lan>
Date: Thu, 18 May 2023 12:48:18 -0400
From: Kent Overstreet <kent.overstreet@...ux.dev>
To: Song Liu <song@...nel.org>
Cc: Mike Rapoport <rppt@...nel.org>, linux-mm@...ck.org,
Andrew Morton <akpm@...ux-foundation.org>,
Dave Hansen <dave.hansen@...ux.intel.com>,
Peter Zijlstra <peterz@...radead.org>,
Rick Edgecombe <rick.p.edgecombe@...el.com>,
Thomas Gleixner <tglx@...utronix.de>,
Vlastimil Babka <vbabka@...e.cz>, linux-kernel@...r.kernel.org,
x86@...nel.org
Subject: Re: [RFC PATCH 1/5] mm: intorduce __GFP_UNMAPPED and unmapped_alloc()
On Thu, May 18, 2023 at 09:33:20AM -0700, Song Liu wrote:
> I am working on patches based on the discussion in [1]. I am planning to
> send v1 for review in a week or so.
Hey Song, I was reviewing that thread too,
Are you taking a different approach based on Thomas's feedback? I think
he had some fair points in that thread.
My own feeling is that the buddy allocator is our tool for allocating
larger variable sized physically contiguous allocations, so I'd like to
see something based on that - I think we could do a hybrid buddy/slab
allocator approach, like we have for regular memory allocations.
I started on a slab allocator for executable memory allocations the
other day (very minimal, but tested it for bcachefs and it works).
But I'd love to hear more about your current approach as well.
Cheers,
Kent
Powered by blists - more mailing lists