From: Glauber Costa <glommer-bzQdu9zFT3WakBO8gow8eQ@public.gmane.org>
To: Kamezawa Hiroyuki
<kamezawa.hiroyu-+CUm20s59erQFUHtdCDX3A@public.gmane.org>
Cc: linux-mm-Bw31MaZKKs3YtjvyW6yDsg@public.gmane.org,
Michal Hocko <mhocko-AlSwsSmVLrQ@public.gmane.org>,
Johannes Weiner <hannes-druUgvl0LCNAfugRpC6u6w@public.gmane.org>,
Andrew Morton
<akpm-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org>,
cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Tejun Heo <tj-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
Subject: Re: [PATCH] memcg: implement boost mode
Date: Mon, 1 Apr 2013 13:30:22 +0400 [thread overview]
Message-ID: <515953AE.3000403@parallels.com> (raw)
In-Reply-To: <51595311.7070509-+CUm20s59erQFUHtdCDX3A@public.gmane.org>
On 04/01/2013 01:27 PM, Kamezawa Hiroyuki wrote:
> (2013/04/01 16:34), Glauber Costa wrote:
>> There are scenarios in which we would like our programs to run faster.
>> It is a hassle, when they are contained in memcg, that some of its
>> allocations will fail and start triggering reclaim. This is not good
>> for the program, that will now be slower.
>>
>> This patch implements boost mode for memcg. It exposes a u64 file
>> "memcg boost". Every time you write anything to it, it will reduce the
>> counters by ~20 %. Note that we don't want to actually reclaim pages,
>> which would defeat the very goal of boost mode. We just make the
>> res_counters able to accomodate more.
>>
>> This file is also available in the root cgroup. But with a slightly
>> different effect. Writing to it will make more memory physically
>> available so our programs can profit.
>>
>> Please ack and apply.
>>
> Nack.
>
>> Signed-off-by: Glauber Costa <glommer-bzQdu9zFT3WakBO8gow8eQ@public.gmane.org>
>
> Please update limit temporary. If you need call-shrink-explicitly-by-user,
> I think you can add it.
>
I don't want to shrink memory because that will make applications
slower. I want them to be faster, so they need to have more memory.
There is solid research backing up my approach:
http://www.dilbert.com/fast/2008-05-08/
WARNING: multiple messages have this Message-ID (diff)
From: Glauber Costa <glommer@parallels.com>
To: Kamezawa Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Cc: linux-mm@kvack.org, Michal Hocko <mhocko@suse.cz>,
Johannes Weiner <hannes@cmpxchg.org>,
Andrew Morton <akpm@linux-foundation.org>,
cgroups@vger.kernel.org, Tejun Heo <tj@kernel.org>
Subject: Re: [PATCH] memcg: implement boost mode
Date: Mon, 1 Apr 2013 13:30:22 +0400 [thread overview]
Message-ID: <515953AE.3000403@parallels.com> (raw)
In-Reply-To: <51595311.7070509@jp.fujitsu.com>
On 04/01/2013 01:27 PM, Kamezawa Hiroyuki wrote:
> (2013/04/01 16:34), Glauber Costa wrote:
>> There are scenarios in which we would like our programs to run faster.
>> It is a hassle, when they are contained in memcg, that some of its
>> allocations will fail and start triggering reclaim. This is not good
>> for the program, that will now be slower.
>>
>> This patch implements boost mode for memcg. It exposes a u64 file
>> "memcg boost". Every time you write anything to it, it will reduce the
>> counters by ~20 %. Note that we don't want to actually reclaim pages,
>> which would defeat the very goal of boost mode. We just make the
>> res_counters able to accomodate more.
>>
>> This file is also available in the root cgroup. But with a slightly
>> different effect. Writing to it will make more memory physically
>> available so our programs can profit.
>>
>> Please ack and apply.
>>
> Nack.
>
>> Signed-off-by: Glauber Costa <glommer@parallels.com>
>
> Please update limit temporary. If you need call-shrink-explicitly-by-user,
> I think you can add it.
>
I don't want to shrink memory because that will make applications
slower. I want them to be faster, so they need to have more memory.
There is solid research backing up my approach:
http://www.dilbert.com/fast/2008-05-08/
--
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>
next prev parent reply other threads:[~2013-04-01 9:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-01 7:34 [PATCH] memcg: implement boost mode Glauber Costa
2013-04-01 7:34 ` Glauber Costa
[not found] ` <1364801670-10241-1-git-send-email-glommer-bzQdu9zFT3WakBO8gow8eQ@public.gmane.org>
2013-04-01 9:27 ` Kamezawa Hiroyuki
2013-04-01 9:27 ` Kamezawa Hiroyuki
[not found] ` <51595311.7070509-+CUm20s59erQFUHtdCDX3A@public.gmane.org>
2013-04-01 9:30 ` Glauber Costa [this message]
2013-04-01 9:30 ` Glauber Costa
[not found] ` <515953AE.3000403-bzQdu9zFT3WakBO8gow8eQ@public.gmane.org>
2013-04-01 9:37 ` Michal Hocko
2013-04-01 9:37 ` Michal Hocko
[not found] ` <20130401093740.GA30749-2MMpYkNvuYDjFM9bn6wA6Q@public.gmane.org>
2013-04-01 10:02 ` Kamezawa Hiroyuki
2013-04-01 10:02 ` Kamezawa Hiroyuki
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=515953AE.3000403@parallels.com \
--to=glommer-bzqdu9zft3wakbo8gow8eq@public.gmane.org \
--cc=akpm-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org \
--cc=cgroups-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=hannes-druUgvl0LCNAfugRpC6u6w@public.gmane.org \
--cc=kamezawa.hiroyu-+CUm20s59erQFUHtdCDX3A@public.gmane.org \
--cc=linux-mm-Bw31MaZKKs3YtjvyW6yDsg@public.gmane.org \
--cc=mhocko-AlSwsSmVLrQ@public.gmane.org \
--cc=tj-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org \
/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.