[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190902080218.GF14028@dhcp22.suse.cz>
Date: Mon, 2 Sep 2019 10:02:18 +0200
From: Michal Hocko <mhocko@...nel.org>
To: Khalid Aziz <khalid.aziz@...cle.com>
Cc: Bharath Vedartham <linux.bhar@...il.com>,
akpm@...ux-foundation.org, vbabka@...e.cz,
mgorman@...hsingularity.net, dan.j.williams@...el.com,
osalvador@...e.de, richard.weiyang@...il.com, hannes@...xchg.org,
arunks@...eaurora.org, rppt@...ux.vnet.ibm.com, jgg@...pe.ca,
amir73il@...il.com, alexander.h.duyck@...ux.intel.com,
linux-mm@...ck.org, linux-kernel-mentees@...ts.linuxfoundation.org,
linux-kernel@...r.kernel.org
Subject: Re: [RFC PATCH 0/2] Add predictive memory reclamation and compaction
On Fri 30-08-19 15:35:06, Khalid Aziz wrote:
[...]
> - Kernel is not self-tuning and is dependent upon a userspace tool to
> perform well in a fundamental area of memory management.
You keep bringing this up without an actual analysis of a wider range of
workloads that would prove that the default behavior is really
suboptimal. You are making some assumptions based on a very specific DB
workload which might benefit from a more aggressive background workload.
If you really want to sell any changes to auto tuning then you really
need to come up with more workloads and an actual theory why an early
and more aggressive reclaim pays off.
--
Michal Hocko
SUSE Labs
Powered by blists - more mailing lists