[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAB6CXpAGTWGNboAXEkqC2wZsHmvbhFf_5enguXJ7QssRpr=c9A@mail.gmail.com>
Date: Tue, 9 Jun 2020 11:37:31 -0700
From: Nitin Gupta <ngupta@...ingupta.dev>
To: Vlastimil Babka <vbabka@...e.cz>,
Andrew Morton <akpm@...ux-foundation.org>
Cc: Mel Gorman <mgorman@...hsingularity.net>,
Michal Hocko <mhocko@...e.com>,
Nitin Gupta <nigupta@...dia.com>,
Matthew Wilcox <willy@...radead.org>,
Mike Kravetz <mike.kravetz@...cle.com>,
Joonsoo Kim <iamjoonsoo.kim@....com>,
David Rientjes <rientjes@...gle.com>,
linux-kernel <linux-kernel@...r.kernel.org>,
linux-mm <linux-mm@...ck.org>,
Linux API <linux-api@...r.kernel.org>,
Khalid Aziz <khalid.aziz@...cle.com>
Subject: Re: [PATCH v6] mm: Proactive compaction
On Mon, Jun 1, 2020 at 12:48 PM Nitin Gupta <nigupta@...dia.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.
>
> Signed-off-by: Nitin Gupta <nigupta@...dia.com>
> Reviewed-by: Vlastimil Babka <vbabka@...e.cz>
(+CC Khalid)
Can this be pipelined for upstream inclusion now? Sorry, I'm a bit
rusty on upstream flow these days.
Thanks,
Nitin
Powered by blists - more mailing lists