linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Michal Hocko <mhocko@kernel.org>
To: Pankaj Suryawanshi <pankajssuryawanshi@gmail.com>
Cc: Vlastimil Babka <vbabka@suse.cz>,
	linux-kernel@vger.kernel.org, linux-mm@kvack.org,
	pankaj.suryawanshi@einfochips.com
Subject: Re: oom-killer
Date: Tue, 6 Aug 2019 17:11:23 +0200	[thread overview]
Message-ID: <20190806151123.GI11812@dhcp22.suse.cz> (raw)
In-Reply-To: <CACDBo57Yjuc69GX+V7w_efSHPkpeU3D9RUr0TEd64oUTi4o8Ag@mail.gmail.com>

On Tue 06-08-19 20:25:51, Pankaj Suryawanshi wrote:
[...]
> lowmem reserve ? it is min_free_kbytes or something else.

Nope. Lowmem rezerve is a measure to protect from allocations targetting
higher zones (have a look at setup_per_zone_lowmem_reserve). The value
for each zone depends on the amount of memory managed by the zone
and the ratio which can be tuned from the userspace. min_free_kbytes
controls reclaim watermarks.

-- 
Michal Hocko
SUSE Labs


      reply	other threads:[~2019-08-06 15:11 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-03 13:23 oom-killer Pankaj Suryawanshi
2019-08-05 11:24 ` oom-killer Michal Hocko
2019-08-05 11:56   ` oom-killer Vlastimil Babka
2019-08-05 12:05     ` oom-killer Michal Hocko
2019-08-05 15:34       ` oom-killer Pankaj Suryawanshi
2019-08-05 20:16         ` oom-killer Michal Hocko
2019-08-06 14:54           ` oom-killer Pankaj Suryawanshi
2019-08-06 15:07             ` oom-killer Michal Hocko
2019-08-06 15:09               ` oom-killer Pankaj Suryawanshi
2019-08-06 15:12                 ` oom-killer Michal Hocko
2019-08-06 15:23                   ` oom-killer Pankaj Suryawanshi
2019-08-06 10:04         ` oom-killer Vlastimil Babka
2019-08-06 14:55           ` oom-killer Pankaj Suryawanshi
2019-08-06 15:11             ` Michal Hocko [this message]

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=20190806151123.GI11812@dhcp22.suse.cz \
    --to=mhocko@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=pankaj.suryawanshi@einfochips.com \
    --cc=pankajssuryawanshi@gmail.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