From: David Hildenbrand <david@redhat.com>
To: "孙世龙 sunshilong" <sunshilong369@gmail.com>, linux-mm@kvack.org
Subject: Re: 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: Wed, 24 Jun 2020 11:53:03 +0200 [thread overview]
Message-ID: <73b5db17-805a-4f1a-60f7-26695c0422e8@redhat.com> (raw)
In-Reply-To: <CAAvDm6Zf5ejTPzpEPAa0kLyTyEZkD9y6D-2qhs3CcN0t+73Ybw@mail.gmail.com>
On 23.06.20 17:52, 孙世龙 sunshilong wrote:
> 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?
We do have mobility grouping on pageblock order.
Also, I think you can use ZONE_MOVABLE without migration and compaction,
to at least locally limit unmovable fragmentation.
>
> Are there some system settings that could make for this goal?
Why don't you want page compaction/migration?
--
Thanks,
David / dhildenb
next prev parent reply other threads:[~2020-06-24 9:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
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
-- strict thread matches above, loose matches on Subject: below --
2020-06-23 15:39 孙世龙 sunshilong
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=73b5db17-805a-4f1a-60f7-26695c0422e8@redhat.com \
--to=david@redhat.com \
--cc=linux-mm@kvack.org \
--cc=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).