[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20080924143217.9B2E.KOSAKI.MOTOHIRO@jp.fujitsu.com>
Date: Wed, 24 Sep 2008 15:59:01 +0900 (JST)
From: KOSAKI Motohiro <kosaki.motohiro@...fujitsu.com>
To: "Michael Rubin" <mrubin@...gle.com>
Cc: kosaki.motohiro@...fujitsu.com,
"Andrew Morton" <akpm@...ux-foundation.org>, dradford@...ehost.com,
m.innocenti@...eca.it, fernando@....ntt.co.jp,
containers@...ts.linux-foundation.org,
linux-kernel@...r.kernel.org, chlunde@...g.uio.no,
dave@...ux.vnet.ibm.com, dpshah@...gle.com, agk@...rceware.org,
matt@...ehost.com, menage@...gle.com,
"Andrea Righi" <righi.andrea@...il.com>, eric.rannaud@...il.com,
balbir@...ux.vnet.ibm.com
Subject: Re: [RFC] [PATCH -mm 0/2] memcg: per cgroup dirty_ratio
> > We don't have any motivation of its interface change.
>
> We are seeing problems where we are generating a lot of dirty memory
> from asynchronous background writes while more important traffic is
> operating with DIRECT_IO. The DIRECT_IO traffic will incur high
> latency spikes as the pdflush hits the background threshold and tries
> to write a lot of dirty buffers at once.
>
> What we want to do is lower the background threshold low enough so
> that we don't end up writing a lot of data at one time. As systems get
> more and more memory this is and will become difficult. 1% of system
> RAM could tie up a disk.
yup.
sorry, I choosed bad word at my last mail. it caused your confusion.
I only disagreed vm_dirty_KB.
I agreed with fine graind vm_dirty_ratio.
Thanks.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists