From: Michal Hocko <mhocko@kernel.org>
To: Bharath Vedartham <linux.bhar@gmail.com>
Cc: Khalid Aziz <khalid.aziz@oracle.com>,
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, 28 Aug 2019 15:15:01 +0200 [thread overview]
Message-ID: <20190828131501.GK28313@dhcp22.suse.cz> (raw)
In-Reply-To: <20190828130922.GA10127@bharath12345-Inspiron-5559>
On Wed 28-08-19 18:39:22, Bharath Vedartham wrote:
[...]
> > Therefore I would like to shift the discussion towards existing APIs and
> > whether they are suitable for such an advance auto-tuning. I haven't
> > heard any arguments about missing pieces.
> I understand your concern here. Just confirming, by APIs you are
> referring to sysctls, sysfs files and stuff like that right?
Yup
> > > If memory exhaustion
> > > occurs, we reclaim some more memory. kswapd stops reclaim when
> > > hwmark is reached. hwmark is usually set to a fairly low percentage of
> > > total memory, in my system for zone Normal hwmark is 13% of total pages.
> > > So there is scope for reclaiming more pages to make sure system does not
> > > suffer from a lack of pages.
> >
> > Yes and we have ways to control those watermarks that your monitoring
> > tool can use to alter the reclaim behavior.
> Just to confirm here, I am aware of one way which is to alter
> min_kfree_bytes values. What other ways are there to alter watermarks
> from user space?
/proc/sys/vm/watermark_*factor
--
Michal Hocko
SUSE Labs
next prev parent reply other threads:[~2019-08-28 13:15 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-13 1:40 [RFC PATCH 0/2] Add predictive memory reclamation and compaction 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
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 [this message]
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=20190828131501.GK28313@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=linux.bhar@gmail.com \
--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;
as well as URLs for NNTP newsgroup(s).