From: Michal Hocko <mhocko@kernel.org>
To: Khalid Aziz <khalid.aziz@oracle.com>
Cc: akpm@linux-foundation.org, vbabka@suse.cz,
mgorman@techsingularity.net, dan.j.williams@intel.com,
osalvador@suse.de, richard.weiyang@gmail.com, hannes@cmpxchg.org,
arunks@codeaurora.org, rppt@linux.vnet.ibm.com, jgg@ziepe.ca,
amir73il@gmail.com, alexander.h.duyck@linux.intel.com,
linux-mm@kvack.org,
linux-kernel-mentees@lists.linuxfoundation.org,
linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH 0/2] Add predictive memory reclamation and compaction
Date: Wed, 21 Aug 2019 16:06:32 +0200 [thread overview]
Message-ID: <20190821140632.GI3111@dhcp22.suse.cz> (raw)
In-Reply-To: <2668ad2e-ee52-8c88-22c0-1952243af5a1@oracle.com>
On Thu 15-08-19 14:51:04, Khalid Aziz wrote:
> Hi Michal,
>
> The smarts for tuning these knobs can be implemented in userspace and
> more knobs added to allow for what is missing today, but we get back to
> the same issue as before. That does nothing to make kernel self-tuning
> and adds possibly even more knobs to userspace. Something so fundamental
> to kernel memory management as making free pages available when they are
> needed really should be taken care of in the kernel itself. Moving it to
> userspace just means the kernel is hobbled unless one installs and tunes
> a userspace package correctly.
From my past experience the existing autotunig works mostly ok for a
vast variety of workloads. A more clever tuning is possible and people
are doing that already. Especially for cases when the machine is heavily
overcommited. There are different ways to achieve that. Your new
in-kernel auto tuning would have to be tested on a large variety of
workloads to be proven and riskless. So I am quite skeptical to be
honest.
Therefore I would really focus on discussing whether we have sufficient
APIs to tune the kernel to do the right thing when needed. That requires
to identify gaps in that area.
--
Michal Hocko
SUSE Labs
next prev parent reply other threads:[~2019-08-21 14:06 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-13 1:40 Khalid Aziz
2019-08-13 1:40 ` [RFC PATCH 1/2] mm: Add trend based prediction algorithm for memory usage Khalid Aziz
2019-08-13 1:40 ` [RFC PATCH 2/2] mm/vmscan: Add fragmentation and page starvation prediction to kswapd Khalid Aziz
2019-08-13 14:05 ` [RFC PATCH 0/2] Add predictive memory reclamation and compaction Michal Hocko
2019-08-13 15:20 ` Khalid Aziz
2019-08-14 8:58 ` Michal Hocko
2019-08-15 16:27 ` Khalid Aziz
2019-08-15 17:02 ` Michal Hocko
2019-08-15 20:51 ` Khalid Aziz
2019-08-21 14:06 ` Michal Hocko [this message]
2019-08-26 20:44 ` Bharath Vedartham
2019-08-27 6:16 ` Michal Hocko
2019-08-28 13:09 ` Bharath Vedartham
2019-08-28 13:15 ` Michal Hocko
2019-08-30 21:35 ` Khalid Aziz
2019-09-02 8:02 ` Michal Hocko
2019-09-03 19:45 ` Khalid Aziz
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=20190821140632.GI3111@dhcp22.suse.cz \
--to=mhocko@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=alexander.h.duyck@linux.intel.com \
--cc=amir73il@gmail.com \
--cc=arunks@codeaurora.org \
--cc=dan.j.williams@intel.com \
--cc=hannes@cmpxchg.org \
--cc=jgg@ziepe.ca \
--cc=khalid.aziz@oracle.com \
--cc=linux-kernel-mentees@lists.linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@techsingularity.net \
--cc=osalvador@suse.de \
--cc=richard.weiyang@gmail.com \
--cc=rppt@linux.vnet.ibm.com \
--cc=vbabka@suse.cz \
/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