From: dev12124 <joaoanandalima@gmail.com>
To: linux-mm@kvack.org, linux-kernel@vger.kernel.org
Cc: vbabka@suse.cz, david@redhat.com, hch@lst.de
Subject: [RFC] mm: alloc__by: create a function for allocate pages in small microsseconds in boards no-MMU
Date: Fri, 20 Nov 2026 03:08:38 -0300 (Hora oficial do Brasil) [thread overview]
Message-ID: <1ee9b247-6758-c146-2d03-0acea98db33f@gmail.com> (raw)
[-- 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>
reply other threads:[~2026-11-20 6:08 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1ee9b247-6758-c146-2d03-0acea98db33f@gmail.com \
--to=joaoanandalima@gmail.com \
--cc=david@redhat.com \
--cc=hch@lst.de \
--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