From: Nitin Gupta <ngupta@nitingupta.dev>
To: Nitin Gupta <nigupta@nvidia.com>
Cc: Mel Gorman <mgorman@techsingularity.net>,
Michal Hocko <mhocko@suse.com>, Vlastimil Babka <vbabka@suse.cz>,
Matthew Wilcox <willy@infradead.org>,
Andrew Morton <akpm@linux-foundation.org>,
Mike Kravetz <mike.kravetz@oracle.com>,
Joonsoo Kim <iamjoonsoo.kim@lge.com>,
David Rientjes <rientjes@google.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
linux-mm <linux-mm@kvack.org>,
Linux API <linux-api@vger.kernel.org>
Subject: Re: [PATCH v5] mm: Proactive compaction
Date: Tue, 26 May 2020 10:19:18 -0700 [thread overview]
Message-ID: <CAB6CXpDh62SQuice+Oa3L+ggE9SzSkbeKCqwcB-yqF-NVrWnUQ@mail.gmail.com> (raw)
In-Reply-To: <20200518181446.25759-1-nigupta@nvidia.com>
[-- Attachment #1: Type: text/plain, Size: 1207 bytes --]
On Mon, May 18, 2020 at 11:14 AM Nitin Gupta <nigupta@nvidia.com> wrote:
> For some applications, we need to allocate almost all memory as
> hugepages. However, on a running system, higher-order allocations can
> fail if the memory is fragmented. Linux kernel currently does on-demand
> compaction as we request more hugepages, but this style of compaction
> incurs very high latency. Experiments with one-time full memory
> compaction (followed by hugepage allocations) show that kernel is able
> to restore a highly fragmented memory state to a fairly compacted memory
> state within <1 sec for a 32G system. Such data suggests that a more
> proactive compaction can help us allocate a large fraction of memory as
> hugepages keeping allocation latencies low.
>
> For a more proactive compaction, the approach taken here is to define
> a new tunable called 'proactiveness' which dictates bounds for external
> fragmentation wrt HUGETLB_PAGE_ORDER order which kcompactd tries to
> maintain.
>
> The tunable is exposed through sysctl:
> /proc/sys/vm/compaction_proactiveness
>
> It takes value in range [0, 100], with a default of 20.
>
>
Ping.
Any comments/feedback for this v5 patch?
Thanks,
Nitin
[-- Attachment #2: Type: text/html, Size: 1714 bytes --]
next prev parent reply other threads:[~2020-05-26 17:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-18 18:14 Nitin Gupta
2020-05-26 17:19 ` Nitin Gupta [this message]
2020-05-27 10:18 ` Vlastimil Babka
2020-05-28 21:29 ` Nitin Gupta
2020-05-28 9:15 ` Holger Hoffstätte
2020-05-28 9:50 ` Vlastimil Babka
2020-05-28 17:38 ` Nitin Gupta
2020-05-28 23:29 ` Khalid Aziz
2020-05-29 0:55 ` Nitin Gupta
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=CAB6CXpDh62SQuice+Oa3L+ggE9SzSkbeKCqwcB-yqF-NVrWnUQ@mail.gmail.com \
--to=ngupta@nitingupta.dev \
--cc=akpm@linux-foundation.org \
--cc=iamjoonsoo.kim@lge.com \
--cc=linux-api@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@techsingularity.net \
--cc=mhocko@suse.com \
--cc=mike.kravetz@oracle.com \
--cc=nigupta@nvidia.com \
--cc=rientjes@google.com \
--cc=vbabka@suse.cz \
--cc=willy@infradead.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