From: Andrea Righi <righi.andrea@gmail.com>
To: Dave Hansen <dave@linux.vnet.ibm.com>
Cc: "Balbir Singh" <balbir@linux.vnet.ibm.com>,
"Paul Menage" <menage@google.com>,
"KAMEZAWA Hiroyuki" <kamezawa.hiroyu@jp.fujitsu.com>,
"David Radford" <dradford@bluehost.com>,
"Marco Innocenti" <m.innocenti@cineca.it>,
"Fernando Luis Vázquez Cao" <fernando@oss.ntt.co.jp>,
containers@lists.linux-foundation.org,
LKML <linux-kernel@vger.kernel.org>,
"Carl Henrik Lunde" <chlunde@ping.uio.no>,
linux-mm@kvack.org, "Divyesh Shah" <dpshah@google.com>,
"Matt Heaton" <matt@bluehost.com>,
"Andrew Morton" <akpm@linux-foundation.org>,
"Naveen Gupta" <ngupta@google.com>
Subject: Re: [RFC] [PATCH -mm] cgroup: limit the amount of dirty file pages
Date: Wed, 10 Sep 2008 09:26:40 +0200 [thread overview]
Message-ID: <48C776B0.9070703@gmail.com> (raw)
In-Reply-To: <1220982584.23386.219.camel@nimitz>
Dave Hansen wrote:
> On Tue, 2008-09-09 at 17:38 +0200, Andrea Righi wrote:
>> It allows to control how much dirty file pages a cgroup can have at any
>> given time. This feature is supposed to be strictly connected to a
>> generic cgroup IO controller (see below).
>
> So, this functions similarly to our global dirty ratio? Is it just
> intended to keep a cgroup from wedging itself too hard with too many
> dirty pages, just like the global ratio?
>
> -- Dave
Correct, it's the same functionality provided by vm.dirty_ratio and
vm.dirty_background_ratio, except that is intended to be per-cgroup.
Without this functionality, a cgroup can even dirty all its memory,
allocated by the memory controller, since statistics and writeback
configurations are global.
-Andrea
WARNING: multiple messages have this Message-ID (diff)
From: Andrea Righi <righi.andrea@gmail.com>
To: Dave Hansen <dave@linux.vnet.ibm.com>
Cc: "Balbir Singh" <balbir@linux.vnet.ibm.com>,
"Paul Menage" <menage@google.com>,
"KAMEZAWA Hiroyuki" <kamezawa.hiroyu@jp.fujitsu.com>,
"David Radford" <dradford@bluehost.com>,
"Marco Innocenti" <m.innocenti@cineca.it>,
"Fernando Luis Vázquez Cao" <fernando@oss.ntt.co.jp>,
containers@lists.linux-foundation.org,
LKML <linux-kernel@vger.kernel.org>,
"Carl Henrik Lunde" <chlunde@ping.uio.no>,
linux-mm@kvack.org, "Divyesh Shah" <dpshah@google.com>,
"Matt Heaton" <matt@bluehost.com>,
"Andrew Morton" <akpm@linux-foundation.org>,
"Naveen Gupta" <ngupta@google.com>
Subject: Re: [RFC] [PATCH -mm] cgroup: limit the amount of dirty file pages
Date: Wed, 10 Sep 2008 09:26:40 +0200 [thread overview]
Message-ID: <48C776B0.9070703@gmail.com> (raw)
In-Reply-To: <1220982584.23386.219.camel@nimitz>
Dave Hansen wrote:
> On Tue, 2008-09-09 at 17:38 +0200, Andrea Righi wrote:
>> It allows to control how much dirty file pages a cgroup can have at any
>> given time. This feature is supposed to be strictly connected to a
>> generic cgroup IO controller (see below).
>
> So, this functions similarly to our global dirty ratio? Is it just
> intended to keep a cgroup from wedging itself too hard with too many
> dirty pages, just like the global ratio?
>
> -- Dave
Correct, it's the same functionality provided by vm.dirty_ratio and
vm.dirty_background_ratio, except that is intended to be per-cgroup.
Without this functionality, a cgroup can even dirty all its memory,
allocated by the memory controller, since statistics and writeback
configurations are global.
-Andrea
--
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:[~2008-09-10 7:26 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-09 15:38 [RFC] [PATCH -mm] cgroup: limit the amount of dirty file pages Andrea Righi
2008-09-09 15:38 ` Andrea Righi
2008-09-09 16:26 ` kamezawa.hiroyu
2008-09-09 16:26 ` kamezawa.hiroyu
2008-09-09 16:39 ` Andrea Righi
2008-09-09 16:39 ` Andrea Righi
[not found] ` <11118085.1220977593430.kamezawa.hiroyu-+CUm20s59erQFUHtdCDX3A@public.gmane.org>
2008-09-09 16:39 ` Andrea Righi
[not found] ` <48C6987D.2050905-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2008-09-09 16:26 ` kamezawa.hiroyu-+CUm20s59erQFUHtdCDX3A
2008-09-09 17:49 ` Dave Hansen
2008-09-09 17:49 ` Dave Hansen
2008-09-09 17:49 ` Dave Hansen
2008-09-10 7:26 ` Andrea Righi [this message]
2008-09-10 7:26 ` Andrea Righi
2008-09-10 7:26 ` Andrea Righi
-- strict thread matches above, loose matches on Subject: below --
2008-09-09 15:38 Andrea Righi
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=48C776B0.9070703@gmail.com \
--to=righi.andrea@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=balbir@linux.vnet.ibm.com \
--cc=chlunde@ping.uio.no \
--cc=containers@lists.linux-foundation.org \
--cc=dave@linux.vnet.ibm.com \
--cc=dpshah@google.com \
--cc=dradford@bluehost.com \
--cc=fernando@oss.ntt.co.jp \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=m.innocenti@cineca.it \
--cc=matt@bluehost.com \
--cc=menage@google.com \
--cc=ngupta@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.