From: Infinity <chaojibjt@qq.com>
To: linux-mm <linux-mm@kvack.org>
Subject: [HELP] Request for assistance to upstream an Android memory optimization (Multi_Freearea)
Date: Sun, 18 Jan 2026 16:58:36 +0800 [thread overview]
Message-ID: <tencent_1B6C070183FB1FEA24C7AF846403A868B00A@qq.com> (raw)
Hello,
I am a non-technical user who came across an interesting memory optimization
in the Android kernel tree, and I'm seeking guidance on whether/how it might
be considered for upstream inclusion.
Optimization: Multi_Freearea
Link: https://android-review.googlesource.com/c/kernel/common/+/2942530
Brief description:
- Divides memory into segments by PFN range to reduce external fragmentation
- Tested on Android with kernel 5.10, showing 95.6% reduction in COMPACTSTALL
- Author: lipeifeng from OPPO
As I'm not a kernel developer, I'm reaching out to ask:
1. Is this type of optimization potentially suitable for mainline?
2. What would be the proper process to have it evaluated?
3. Could someone with expertise in memory management take a look?
I understand this may not be the typical technical patch submission, but I
believe the optimization has merit and wanted to bring it to attention.
Thank you for any guidance you can provide.
Sincerely,
John
next reply other threads:[~2026-01-18 8:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-18 8:58 Infinity [this message]
2026-01-19 16:17 ` Matthew Wilcox
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=tencent_1B6C070183FB1FEA24C7AF846403A868B00A@qq.com \
--to=chaojibjt@qq.com \
--cc=linux-mm@kvack.org \
/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