mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "David Hildenbrand (Arm)" <david@kernel.org>
To: dev12124 <joaoanandalima@gmail.com>,
	linux-mm@kvack.org, linux-kernel@vger.kernel.org
Cc: vbabka@suse.cz, hch@lst.de
Subject: Re: [RFC] mm: alloc__by: create a function for allocate pages in small microsseconds in boards no-MMU
Date: Fri, 20 Nov 2026 09:57:28 +0100	[thread overview]
Message-ID: <4ed0eeda-22bd-4489-ad18-d522b36d22be@kernel.org> (raw)
In-Reply-To: <1ee9b247-6758-c146-2d03-0acea98db33f@gmail.com>

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

      reply	other threads:[~2026-11-20  8:57 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-20  6:08 dev12124
2026-11-20  8:57 ` David Hildenbrand (Arm) [this message]

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=4ed0eeda-22bd-4489-ad18-d522b36d22be@kernel.org \
    --to=david@kernel.org \
    --cc=hch@lst.de \
    --cc=joaoanandalima@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --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

all inboxes | Powered by JetHome®