All of lore.kernel.org
 help / color / mirror / Atom feed
* [RFC] mm: alloc__by: create a function for allocate pages in small microsseconds in boards no-MMU
@ 2026-11-20  6:08 dev12124
  2026-11-20  8:57 ` David Hildenbrand (Arm)
  0 siblings, 1 reply; 3+ messages in thread
From: dev12124 @ 2026-11-20  6:08 UTC (permalink / raw)
  To: linux-mm, linux-kernel; +Cc: vbabka, david, hch

[-- Attachment #1: Type: text/plain, Size: 1402 bytes --]


Hi memory subsystem,

Actually, boards no-MMU do not have an integrated MMU to translate 
physical to virtual addresses or support hardware paging and; for this, a 
few points:

I. Requirement for Contiguous Memory
Without an MMU, the kernel cannot combine scattered physical blocks to 
simulate a continuous space, making the search for and allocation of 
larger blocks very slow due to fragmentation.

II. Demand Paging
The system cannot defer physical allocation via page faults; instead, it 
must reserve entire blocks in advance.

III. Use of simplified allocators
such as SLUB_TINY or linear free-list scans (instead of the standard 
SLUB); it saves space by 
scanning simple lists of blocks, but it performs very slowly during 
allocation.

IV. Proposed approach
The function alloc_by(size, address_initial, flag) haves:
* pre-reserved pool per size order;
* cache fast-path no global lock;
* bitmap O(1) of free contiguous blocks.
This bitmap, more specifically the blocks, have the pre-reserved pool (per 
size order)and the pool have word 2:
* Word 1: The initial address (starts in cache fast-path)
* Word 2: The final address.
For example, a Program allocates 277 bytes, the alloc_by() enter and 
verify the bitmap -> viewing the request is 277 bytes, the aproximated 
size is 512 bytes and alloc_by alloc 512 bytes.

Thanks,
João Guilherme da Silva Freitas Lima <joaoanandalima@gmail.com>

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: [RFC] mm: alloc__by: create a function for allocate pages in small microsseconds in boards no-MMU
  2026-11-20  6:08 [RFC] mm: alloc__by: create a function for allocate pages in small microsseconds in boards no-MMU dev12124
@ 2026-11-20  8:57 ` David Hildenbrand (Arm)
  2026-11-20 12:10   ` dev12124
  0 siblings, 1 reply; 3+ messages in thread
From: David Hildenbrand (Arm) @ 2026-11-20  8:57 UTC (permalink / raw)
  To: dev12124, linux-mm, linux-kernel; +Cc: vbabka, hch

On 11/20/26 07:08, dev12124 wrote:
> 
> Hi memory subsystem,
> 
> Actually, boards no-MMU do not have an integrated MMU to translate 
> physical to virtual addresses or support hardware paging and; for this, a 
> few points:
> 
> I. Requirement for Contiguous Memory
> Without an MMU, the kernel cannot combine scattered physical blocks to 
> simulate a continuous space, making the search for and allocation of 
> larger blocks very slow due to fragmentation.
> 
> II. Demand Paging
> The system cannot defer physical allocation via page faults; instead, it 
> must reserve entire blocks in advance.
> 
> III. Use of simplified allocators
> such as SLUB_TINY or linear free-list scans (instead of the standard 
> SLUB); it saves space by 
> scanning simple lists of blocks, but it performs very slowly during 
> allocation.
> 
> IV. Proposed approach
> The function alloc_by(size, address_initial, flag) haves:
> * pre-reserved pool per size order;
> * cache fast-path no global lock;
> * bitmap O(1) of free contiguous blocks.
> This bitmap, more specifically the blocks, have the pre-reserved pool (per 
> size order)and the pool have word 2:
> * Word 1: The initial address (starts in cache fast-path)
> * Word 2: The final address.
> For example, a Program allocates 277 bytes, the alloc_by() enter and 
> verify the bitmap -> viewing the request is 277 bytes, the aproximated 
> size is 512 bytes and alloc_by alloc 512 bytes.

Hi,

I think we are much rather looking into removing NOMMU then optimizing it :)

-- 
Cheers,

David


^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: [RFC] mm: alloc__by: create a function for allocate pages in small microsseconds in boards no-MMU
  2026-11-20  8:57 ` David Hildenbrand (Arm)
@ 2026-11-20 12:10   ` dev12124
  0 siblings, 0 replies; 3+ messages in thread
From: dev12124 @ 2026-11-20 12:10 UTC (permalink / raw)
  To: David Hildenbrand (Arm); +Cc: linux-mm, linux-kernel, vbabka, hch



> On Fri, 20 Nov 2026, David Hildenbrand (Arm) wrote:
>
> Hi,
>
> I think we are much rather looking into removing NOMMU then optimizing it :)
>
> -- 
> Cheers,
>
> David
>

Hi,

Thanks! Ok for the atual focuos! :)


^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2026-11-20 12:10 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2026-11-20  6:08 [RFC] mm: alloc__by: create a function for allocate pages in small microsseconds in boards no-MMU dev12124
2026-11-20  8:57 ` David Hildenbrand (Arm)
2026-11-20 12:10   ` dev12124

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.