linux-kernel - Re: [PATCH 02/35] writeback: safety margin for bdi stat error

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20110112215949.GD14260@quack.suse.cz>
Date:	Wed, 12 Jan 2011 22:59:49 +0100
From:	Jan Kara <jack@...e.cz>
To:	Wu Fengguang <fengguang.wu@...el.com>
Cc:	Andrew Morton <akpm@...ux-foundation.org>, Jan Kara <jack@...e.cz>,
	Peter Zijlstra <a.p.zijlstra@...llo.nl>,
	Christoph Hellwig <hch@....de>,
	Trond Myklebust <Trond.Myklebust@...app.com>,
	Dave Chinner <david@...morbit.com>,
	Theodore Ts'o <tytso@....edu>,
	Chris Mason <chris.mason@...cle.com>,
	Mel Gorman <mel@....ul.ie>, Rik van Riel <riel@...hat.com>,
	KOSAKI Motohiro <kosaki.motohiro@...fujitsu.com>,
	Greg Thelen <gthelen@...gle.com>,
	Minchan Kim <minchan.kim@...il.com>,
	linux-mm <linux-mm@...ck.org>, linux-fsdevel@...r.kernel.org,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 02/35] writeback: safety margin for bdi stat error

On Mon 13-12-10 22:46:48, Wu Fengguang wrote:
> In a simple dd test on a 8p system with "mem=256M", I find all light
> dirtier tasks on the root fs are get heavily throttled. That happens
> because the global limit is exceeded. It's unbelievable at first sight,
> because the test fs doing the heavy dd is under its bdi limit.  After
> doing some tracing, it's discovered that
> 
>         bdi_dirty < bdi_dirty_limit() < global_dirty_limit() < nr_dirty
          ^^ bdi_dirty is the number of pages dirtied on BDI? I.e.
bdi_nr_reclaimable + bdi_nr_writeback?

> So the root cause is, the bdi_dirty is well under the global nr_dirty
> due to accounting errors. This can be fixed by using bdi_stat_sum(),
  So which statistic had the big error? I'd just like to understand
this (and how come your patch improves the situation)...

> however that's costly on large NUMA machines. So do a less costly fix
> of lowering the bdi limit, so that the accounting errors won't lead to
> the absurd situation "global limit exceeded but bdi limit not exceeded".
> 
> This provides guarantee when there is only 1 heavily dirtied bdi, and
> works by opportunity for 2+ heavy dirtied bdi's (hopefully they won't
> reach big error _and_ exceed their bdi limit at the same time).
> 
...
> @@ -458,6 +464,14 @@ unsigned long bdi_dirty_limit(struct bac
>  	long numerator, denominator;
>  
>  	/*
> +	 * try to prevent "global limit exceeded but bdi limit not exceeded"
> +	 */
> +	if (likely(dirty > bdi_stat_error(bdi)))
> +		dirty -= bdi_stat_error(bdi);
> +	else
> +		return 0;
> +
  Ugh, so if by any chance global_dirty_limit() <= bdi_stat_error(bdi), you
will limit number of unreclaimable pages for that bdi 0? Why?

								Honza
-- 
Jan Kara <jack@...e.cz>
SUSE Labs, CR
--
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/