mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Michael Rubin" <mrubin@google.com>
To: "Andrew Morton" <akpm@linux-foundation.org>
Cc: righi.andrea@gmail.com, balbir@linux.vnet.ibm.com,
	menage@google.com, kamezawa.hiroyu@jp.fujitsu.com,
	dave@linux.vnet.ibm.com, chlunde@ping.uio.no, dpshah@google.com,
	eric.rannaud@gmail.com, fernando@oss.ntt.co.jp,
	agk@sourceware.org, m.innocenti@cineca.it,
	s-uchida@ap.jp.nec.com, ryov@valinux.co.jp, matt@bluehost.com,
	dradford@bluehost.com, containers@lists.linux-foundation.org,
	linux-kernel@vger.kernel.org
Subject: Re: [RFC] [PATCH -mm 0/2] memcg: per cgroup dirty_ratio
Date: Mon, 22 Sep 2008 15:26:17 -0700	[thread overview]
Message-ID: <532480950809221526k70fa28edx1d542a9c8a44f810@mail.gmail.com> (raw)
In-Reply-To: <20080912161050.5b6b4065.akpm@linux-foundation.org>

Currently the problme we are hitting is that we cannot specify pdflush
to have background limits less than 1% of memory. I am currently
finishing up a patch right now that adds a dirty_ratio_millis
interface.  I hope to submit the patch to LKML by the end of the week.

The idea is that we don't want to break backwards compatibility and we
also don't want to have two conflicting knobs in the sysctl or
/proc/sys/vm/ space. I thought adding a new knob for those who want to
specify finer grained functionality was a compromise. So the patch has
a vm_dirty_ratio and a vm_dirty_ratio_millis interface. The first to
specify 0-100% and the second to specify .0 to .999%.

So to represent 0.125% of RAM we set
vm_dirty_ratio = 0
vm_dirty_ratio_millis = 125

The same for the background_ratio.

Any feedback?

mrubin

On Fri, Sep 12, 2008 at 4:10 PM, Andrew Morton
<akpm@linux-foundation.org> wrote:
> On Sat, 13 Sep 2008 01:04:35 +0200
> Andrea Righi <righi.andrea@gmail.com> wrote:
>
>> BTW why not use a simple dirty-ratio-in-bytes?
>
> s/ratio/amount/  ;)
>
> No particular reason - I haven't really thought about it frankly.
>
> A "ratio" might make more sense in a containerised setup, particularly
> if the container can be resized on the fly.
>

  reply	other threads:[~2008-09-22 22:26 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 [this message]
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
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=532480950809221526k70fa28edx1d542a9c8a44f810@mail.gmail.com \
    --to=mrubin@google.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=kamezawa.hiroyu@jp.fujitsu.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=m.innocenti@cineca.it \
    --cc=matt@bluehost.com \
    --cc=menage@google.com \
    --cc=righi.andrea@gmail.com \
    --cc=ryov@valinux.co.jp \
    --cc=s-uchida@ap.jp.nec.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®