From: "孙世龙 sunshilong" <sunshilong369@gmail.com>
To: undisclosed-recipients:;
Subject: Are there still some methods that could be used by the Linux kernel to reduce memory fragmentation while both CONFIG-MIGRATION and CONFIG-COMPACTION are disabled?
Date: Tue, 23 Jun 2020 23:39:22 +0800 [thread overview]
Message-ID: <CAAvDm6Yt6omkT2vrd1TESdKHW_QO5XOLq_SSFtQGJafJ5igZ5A@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 226 bytes --]
Are there still some methods that could be used by the Linux kernel
to reduce memory fragmentation while both CONFIG-MIGRATION
and CONFIG-COMPACTION are disabled?
Are there some system settings that could make for this goal?
[-- Attachment #2: Type: text/html, Size: 296 bytes --]
next reply other threads:[~2020-06-23 15:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-23 15:39 孙世龙 sunshilong [this message]
2020-06-23 15:52 Are there still some methods that could be used by the Linux kernel to reduce memory fragmentation while both CONFIG-MIGRATION and CONFIG-COMPACTION are disabled? 孙世龙 sunshilong
2020-06-24 9:53 ` David Hildenbrand
2020-06-24 11:16 ` 孙世龙 sunshilong
2020-06-24 17:22 ` David Rientjes
2020-06-25 3:22 ` 孙世龙 sunshilong
2020-06-28 3:27 ` David Rientjes
2020-06-28 5:15 ` 孙世龙 sunshilong
2020-06-28 20:39 ` David Rientjes
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=CAAvDm6Yt6omkT2vrd1TESdKHW_QO5XOLq_SSFtQGJafJ5igZ5A@mail.gmail.com \
--to=sunshilong369@gmail.com \
/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;
as well as URLs for NNTP newsgroup(s).