From: Anton Vorontsov <anton@enomsg.org>
To: David Rientjes <rientjes@google.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Michal Hocko <mhocko@suse.cz>,
"Kirill A. Shutemov" <kirill@shutemov.name>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [patch] mm, vmpressure: add high level
Date: Wed, 16 Oct 2013 20:05:12 -0700 [thread overview]
Message-ID: <20131017030512.GA21327@teo> (raw)
In-Reply-To: <alpine.DEB.2.02.1310161738410.10147@chino.kir.corp.google.com>
Hello David,
On Wed, Oct 16, 2013 at 05:43:55PM -0700, David Rientjes wrote:
> Vmpressure has two important levels: medium and critical. Medium is
> defined at 60% and critical is defined at 95%.
>
> We have a customer who needs a notification at a higher level than medium,
> which is slight to moderate reclaim activity, and before critical to start
> throttling incoming requests to save memory and avoid oom.
>
> This patch adds the missing link: a high level defined at 80%.
>
> In the future, it would probably be better to allow the user to specify an
> integer ratio for the notification rather than relying on arbitrarily
> specified levels.
Does the customer need to differentiate the two levels (medium and high),
or the customer only interested in this (80%) specific level?
In the latter case, instead of adding a new level I would vote for adding
a [sysfs] knob for modifying medium level's threshold.
Thanks,
Anton
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
WARNING: multiple messages have this Message-ID (diff)
From: Anton Vorontsov <anton@enomsg.org>
To: David Rientjes <rientjes@google.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Michal Hocko <mhocko@suse.cz>,
"Kirill A. Shutemov" <kirill@shutemov.name>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [patch] mm, vmpressure: add high level
Date: Wed, 16 Oct 2013 20:05:12 -0700 [thread overview]
Message-ID: <20131017030512.GA21327@teo> (raw)
In-Reply-To: <alpine.DEB.2.02.1310161738410.10147@chino.kir.corp.google.com>
Hello David,
On Wed, Oct 16, 2013 at 05:43:55PM -0700, David Rientjes wrote:
> Vmpressure has two important levels: medium and critical. Medium is
> defined at 60% and critical is defined at 95%.
>
> We have a customer who needs a notification at a higher level than medium,
> which is slight to moderate reclaim activity, and before critical to start
> throttling incoming requests to save memory and avoid oom.
>
> This patch adds the missing link: a high level defined at 80%.
>
> In the future, it would probably be better to allow the user to specify an
> integer ratio for the notification rather than relying on arbitrarily
> specified levels.
Does the customer need to differentiate the two levels (medium and high),
or the customer only interested in this (80%) specific level?
In the latter case, instead of adding a new level I would vote for adding
a [sysfs] knob for modifying medium level's threshold.
Thanks,
Anton
next prev parent reply other threads:[~2013-10-17 3:05 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-17 0:43 [patch] mm, vmpressure: add high level David Rientjes
2013-10-17 0:43 ` David Rientjes
2013-10-17 3:05 ` Anton Vorontsov [this message]
2013-10-17 3:05 ` Anton Vorontsov
2013-10-17 3:44 ` David Rientjes
2013-10-17 3:44 ` David Rientjes
2013-10-17 3:51 ` [bug] get_maintainer.pl incomplete output David Rientjes
2013-10-17 3:51 ` David Rientjes
2013-10-17 4:03 ` Joe Perches
2013-10-17 4:03 ` Joe Perches
2013-10-17 4:19 ` David Rientjes
2013-10-17 4:19 ` David Rientjes
2013-10-17 4:36 ` Joe Perches
2013-10-17 4:36 ` Joe Perches
2013-10-17 19:12 ` Andrew Morton
2013-10-17 19:12 ` Andrew Morton
2013-10-17 19:23 ` Joe Perches
2013-10-17 19:23 ` Joe Perches
2013-10-18 4:17 ` Joe Perches
2013-10-18 4:17 ` Joe Perches
2013-10-18 22:58 ` David Rientjes
2013-10-18 22:58 ` David Rientjes
2013-10-19 0:25 ` Joe Perches
2013-10-19 0:25 ` Joe Perches
2013-11-14 21:56 ` [PATCH] get_maintainer: Add commit author information to --rolestats Joe Perches
2013-11-14 21:56 ` Joe Perches
2013-11-15 2:16 ` Chen Gang
2013-11-15 2:16 ` Chen Gang
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=20131017030512.GA21327@teo \
--to=anton@enomsg.org \
--cc=akpm@linux-foundation.org \
--cc=kirill@shutemov.name \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.cz \
--cc=rientjes@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.