From: Nitin Gupta <nigupta@nvidia.com>
To: "mgorman@techsingularity.net" <mgorman@techsingularity.net>
Cc: "keescook@chromium.org" <keescook@chromium.org>,
"willy@infradead.org" <willy@infradead.org>,
"aryabinin@virtuozzo.com" <aryabinin@virtuozzo.com>,
"vbabka@suse.cz" <vbabka@suse.cz>,
"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
"hannes@cmpxchg.org" <hannes@cmpxchg.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"cai@lca.pw" <cai@lca.pw>,
"arunks@codeaurora.org" <arunks@codeaurora.org>,
"yuzhao@google.com" <yuzhao@google.com>,
"janne.huttunen@nokia.com" <janne.huttunen@nokia.com>,
"jannh@google.com" <jannh@google.com>,
"gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
"mhocko@suse.com" <mhocko@suse.com>, "guro@fb.com" <guro@fb.com>,
"khlebnikov@yandex-team.ru" <khlebnikov@yandex-team.ru>,
"dan.j.williams@intel.com" <dan.j.williams@intel.com>
Subject: Re: [RFC] mm: Proactive compaction
Date: Thu, 19 Sep 2019 23:22:19 +0000 [thread overview]
Message-ID: <9e24d3fa3098fc338bf396ffdf82555cc033ae48.camel@nvidia.com> (raw)
In-Reply-To: <20190822085135.GS2739@techsingularity.net>
On Thu, 2019-08-22 at 09:51 +0100, Mel Gorman wrote:
> As unappealing as it sounds, I think it is better to try improve the
> allocation latency itself instead of trying to hide the cost in a kernel
> thread. It's far harder to implement as compaction is not easy but it
> would be more obvious what the savings are by looking at a histogram of
> allocation latencies -- there are other metrics that could be considered
> but that's the obvious one.
>
Do you mean reducing allocation latency especially when it hits direct
compaction path? Do you have any ideas in mind for this? I'm open to
working on them and report back latency nummbers, while I think more on less
tunable-heavy background (pro-active) compaction approaches.
-Nitin
next prev parent reply other threads:[~2019-09-19 23:22 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-16 21:43 Nitin Gupta
2019-08-20 8:46 ` Vlastimil Babka
2019-08-20 21:35 ` Nitin Gupta
2019-08-24 7:24 ` Khalid Aziz
2019-09-19 23:37 ` Nitin Gupta
2019-09-24 13:39 ` Vlastimil Babka
2019-09-24 14:11 ` Khalid Aziz
2019-08-20 22:20 ` Matthew Wilcox
2019-08-21 23:23 ` Nitin Gupta
2019-08-22 8:51 ` Mel Gorman
2019-08-22 21:57 ` Nitin Gupta
2019-08-26 11:47 ` Mel Gorman
2019-08-27 20:36 ` Nitin Gupta
2019-09-19 23:22 ` Nitin Gupta [this message]
2019-09-16 20:16 ` David Rientjes
2019-09-16 20:50 ` Nitin Gupta
2019-09-17 19:46 ` John Hubbard
2019-09-17 20:26 ` David Rientjes
2019-11-22 22:31 ` 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=9e24d3fa3098fc338bf396ffdf82555cc033ae48.camel@nvidia.com \
--to=nigupta@nvidia.com \
--cc=akpm@linux-foundation.org \
--cc=arunks@codeaurora.org \
--cc=aryabinin@virtuozzo.com \
--cc=cai@lca.pw \
--cc=dan.j.williams@intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=guro@fb.com \
--cc=hannes@cmpxchg.org \
--cc=janne.huttunen@nokia.com \
--cc=jannh@google.com \
--cc=keescook@chromium.org \
--cc=khlebnikov@yandex-team.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@techsingularity.net \
--cc=mhocko@suse.com \
--cc=vbabka@suse.cz \
--cc=willy@infradead.org \
--cc=yuzhao@google.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