linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Jan Kara <jack@suse.cz>
To: Wu Fengguang <fengguang.wu@intel.com>
Cc: Jan Kara <jack@suse.cz>,
	"linux-mm@kvack.org" <linux-mm@kvack.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Christoph Hellwig <hch@infradead.org>,
	Dave Chinner <david@fromorbit.com>,
	Peter Zijlstra <a.p.zijlstra@chello.nl>
Subject: Re: [PATCH] mm: Properly reflect task dirty limits in dirty_exceeded logic
Date: Mon, 25 Jul 2011 18:04:29 +0200	[thread overview]
Message-ID: <20110725160429.GG6107@quack.suse.cz> (raw)
In-Reply-To: <20110723074344.GA31975@localhost>

On Sat 23-07-11 15:43:45, Wu Fengguang wrote:
> On Fri, Jul 15, 2011 at 05:34:09AM +0800, Jan Kara wrote:
> > > - tasks dirtying close to 25% pages probably cannot be called light
> > >   dirtier and there is no need to protect such tasks
> >   The idea is interesting. The only problem is that we don't want to set
> > dirty_exceeded too late so that heavy dirtiers won't push light dirtiers
> > over their limits so easily due to ratelimiting. It did some computations:
> > We normally ratelimit after 4 MB. Take a low end desktop these days. Say
> > 1 GB of ram, 4 CPUs. So dirty limit will be ~200 MB and the area for task
> > differentiation ~25 MB. We enter balance_dirty_pages() after dirtying
> > num_cpu * ratelimit / 2 pages on average which gives 8 MB. So we should
> > set dirty_exceeded at latest at bdi_dirty / TASK_LIMIT_FRACTION / 2 or
> > task differentiation would have no effect because of ratelimiting.
> > 
> > So we could change the limit to something like:
> > bdi_dirty - min(bdi_dirty / TASK_LIMIT_FRACTION, ratelimit_pages *
> > num_online_cpus / 2 + bdi_dirty / TASK_LIMIT_FRACTION / 16)
> 
> Good analyze!
> 
> > But I'm not sure setups where this would make difference are common...
> 
> I think I'd prefer the original simple patch given that the common
> 1-dirtier is not impacted.
  OK, thanks. So will you merge the patch please?

								Honza
-- 
Jan Kara <jack@suse.cz>
SUSE Labs, CR

--
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/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  reply	other threads:[~2011-07-25 16:04 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-30 18:32 [PATCH] mm: Properly reflect task dirty limits in dirty_exceeded logic Jan Kara
2011-07-04  1:06 ` Wu Fengguang
2011-07-11 17:06   ` Jan Kara
2011-07-13 23:02     ` Wu Fengguang
2011-07-14 21:34       ` Jan Kara
2011-07-23  7:43         ` Wu Fengguang
2011-07-25 16:04           ` Jan Kara [this message]
2011-07-26  4:13             ` Wu Fengguang
2011-07-26 13:57               ` Jan Kara
2011-07-27 14:04                 ` Wu Fengguang
2011-07-27 15:10                   ` Christoph Hellwig
2011-07-28 15:31                   ` Jan Kara

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=20110725160429.GG6107@quack.suse.cz \
    --to=jack@suse.cz \
    --cc=a.p.zijlstra@chello.nl \
    --cc=akpm@linux-foundation.org \
    --cc=david@fromorbit.com \
    --cc=fengguang.wu@intel.com \
    --cc=hch@infradead.org \
    --cc=linux-mm@kvack.org \
    /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;
as well as URLs for NNTP newsgroup(s).