From: yamamoto@valinux.co.jp (YAMAMOTO Takashi)
To: kamezawa.hiroyu@jp.fujitsu.com
Cc: a.p.zijlstra@chello.nl, linux-mm@kvack.org, menage@google.com,
containers@lists.linux-foundation.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH][RFC] dirty balancing for cgroups
Date: Fri, 11 Jul 2008 14:59:26 +0900 (JST) [thread overview]
Message-ID: <20080711055926.9AF4F5A03@siro.lan> (raw)
In-Reply-To: Your message of "Fri, 11 Jul 2008 14:15:11 +0900" <20080711141511.515e69a5.kamezawa.hiroyu@jp.fujitsu.com>
> > > - This looks simple but, could you merge this into memory resource controller ?
> >
> > why?
> >
> 3 points.
> 1. Is this useful if used alone ?
it can be. why not?
> 2. memcg requires this kind of feature, basically.
>
> 3. I wonder I need more work to make this work well under memcg.
i'm not sure if i understand these points. can you explain a bit?
my patch penalizes heavy-writer cgroups as task_dirty_limit does
for heavy-writer tasks. i don't think that it's necessary to be
tied to the memory subsystem because i merely want to group writers.
otoh, if you want to limit the number (or percentage or whatever) of
dirty pages in a memory cgroup, it can't be done independently from
the memory subsystem, of course. it's another story, tho.
YAMAMOTO Takashi
>
> If chasing page->cgroup and memcg make this patch much more complex,
> I think this style of implimentation is a choice.
>
> About 3.
> Does this works well if I changes get_dirty_limit()'s
> determine_dirtyable_memory() calculation under memcg ?
> But to do this seems not valid if dirty_ratio cgroup and memcg cgroup
> containes different set of tasks.
>
> Thanks,
> -Kame
--
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-07-11 5:59 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20080711085449.ba7d14dd.kamezawa.hiroyu@jp.fujitsu.com>
2008-07-11 4:06 ` YAMAMOTO Takashi
2008-07-11 5:15 ` KAMEZAWA Hiroyuki
2008-07-11 5:59 ` YAMAMOTO Takashi [this message]
2008-07-11 7:13 ` KAMEZAWA Hiroyuki
2008-07-11 8:34 ` YAMAMOTO Takashi
2008-07-11 8:52 ` KAMEZAWA Hiroyuki
2008-08-06 8:20 ` YAMAMOTO Takashi
2008-08-06 8:53 ` KAMEZAWA Hiroyuki
2008-08-06 9:10 ` YAMAMOTO Takashi
2008-08-07 13:36 ` Peter Zijlstra
2008-08-13 7:15 ` YAMAMOTO Takashi
2008-08-18 7:58 ` KAMEZAWA Hiroyuki
2008-07-14 13:49 ` Peter Zijlstra
2008-07-17 1:43 ` YAMAMOTO Takashi
2008-08-14 8:38 ` Paul Menage
2008-07-14 14:38 ` kamezawa.hiroyu
[not found] <20080709060034.0CB2D5A29@siro.lan>
2008-07-14 13:37 ` Peter Zijlstra
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=20080711055926.9AF4F5A03@siro.lan \
--to=yamamoto@valinux.co.jp \
--cc=a.p.zijlstra@chello.nl \
--cc=containers@lists.linux-foundation.org \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=menage@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox