mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
To: "Michael Rubin" <mrubin@google.com>
Cc: kosaki.motohiro@jp.fujitsu.com,
	"Andrew Morton" <akpm@linux-foundation.org>,
	dradford@bluehost.com, m.innocenti@cineca.it,
	fernando@oss.ntt.co.jp, containers@lists.linux-foundation.org,
	linux-kernel@vger.kernel.org, chlunde@ping.uio.no,
	dave@linux.vnet.ibm.com, dpshah@google.com, agk@sourceware.org,
	matt@bluehost.com, menage@google.com,
	"Andrea Righi" <righi.andrea@gmail.com>,
	eric.rannaud@gmail.com, balbir@linux.vnet.ibm.com
Subject: Re: [RFC] [PATCH -mm 0/2] memcg: per cgroup dirty_ratio
Date: Wed, 24 Sep 2008 15:59:01 +0900 (JST)	[thread overview]
Message-ID: <20080924143217.9B2E.KOSAKI.MOTOHIRO@jp.fujitsu.com> (raw)
In-Reply-To: <532480950809231321g7be0dd09pe6a32426b361e676@mail.gmail.com>

> > 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.



  reply	other threads:[~2008-09-24  6:59 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-12 15:09 Andrea Righi
2008-09-12 20:18 ` Andrew Morton
2008-09-12 23:04   ` Andrea Righi
2008-09-12 23:10     ` Andrew Morton
2008-09-22 22:26       ` Michael Rubin
2008-09-22 23:41   ` Michael Rubin
2008-09-23 12:50     ` Andrea Righi
2008-09-23 17:48     ` KOSAKI Motohiro
2008-09-23 20:21       ` Michael Rubin
2008-09-24  6:59         ` KOSAKI Motohiro [this message]
2008-10-07 10:35       ` Andrea Righi
2008-10-07 11:04     ` Balbir Singh
2008-10-07 15:49       ` Andrea Righi
2008-10-08  1:16         ` KAMEZAWA Hiroyuki
2008-10-08 13:13           ` Balbir Singh
2008-10-09 15:29             ` [PATCH -mm] page-writeback: fine-grained dirty_ratio and dirty_background_ratio Andrea Righi
2008-10-10  0:41               ` KAMEZAWA Hiroyuki
2008-10-10  9:32                 ` Andrea Righi
2008-10-10 13:13                   ` Andrea Righi
2008-11-10 20:58               ` [PATCH -mm] mm: fine-grained dirty_ratio_pcm and dirty_background_ratio_pcm (v2) Andrea Righi
2008-11-10 21:12                 ` Andrew Morton
2008-11-10 22:03                   ` Andrea Righi
2008-11-10 22:12                     ` Andrew Morton
2008-11-10 22:15                     ` David Rientjes

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=20080924143217.9B2E.KOSAKI.MOTOHIRO@jp.fujitsu.com \
    --to=kosaki.motohiro@jp.fujitsu.com \
    --cc=agk@sourceware.org \
    --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=eric.rannaud@gmail.com \
    --cc=fernando@oss.ntt.co.jp \
    --cc=linux-kernel@vger.kernel.org \
    --cc=m.innocenti@cineca.it \
    --cc=matt@bluehost.com \
    --cc=menage@google.com \
    --cc=mrubin@google.com \
    --cc=righi.andrea@gmail.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
all inboxes | Powered by JetHome®