From: Johannes Weiner <hannes@cmpxchg.org>
To: KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Mel Gorman <mgorman@suse.de>, Rik van Riel <riel@redhat.com>,
Minchan Kim <minchan.kim@gmail.com>,
Michal Hocko <mhocko@suse.cz>,
Christoph Hellwig <hch@infradead.org>,
Wu Fengguang <fengguang.wu@intel.com>,
Dave Chinner <david@fromorbit.com>, Jan Kara <jack@suse.cz>,
Shaohua Li <shaohua.li@intel.com>,
linux-mm@kvack.org, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [patch 3/5] mm: try to distribute dirty pages fairly across zones
Date: Thu, 24 Nov 2011 14:11:55 +0100 [thread overview]
Message-ID: <20111124131155.GB1225@cmpxchg.org> (raw)
In-Reply-To: <20111124100755.d8b783a8.kamezawa.hiroyu@jp.fujitsu.com>
On Thu, Nov 24, 2011 at 10:07:55AM +0900, KAMEZAWA Hiroyuki wrote:
>
>
> Can I make a question ?
>
> On Wed, 23 Nov 2011 14:34:16 +0100
> Johannes Weiner <hannes@cmpxchg.org> wrote:
>
>
> > + /*
> > + * When allocating a page cache page for writing, we
> > + * want to get it from a zone that is within its dirty
> > + * limit, such that no single zone holds more than its
> > + * proportional share of globally allowed dirty pages.
> > + * The dirty limits take into account the zone's
> > + * lowmem reserves and high watermark so that kswapd
> > + * should be able to balance it without having to
> > + * write pages from its LRU list.
> > + *
> > + * This may look like it could increase pressure on
> > + * lower zones by failing allocations in higher zones
> > + * before they are full. But the pages that do spill
> > + * over are limited as the lower zones are protected
> > + * by this very same mechanism. It should not become
> > + * a practical burden to them.
> > + *
> > + * XXX: For now, allow allocations to potentially
> > + * exceed the per-zone dirty limit in the slowpath
> > + * (ALLOC_WMARK_LOW unset) before going into reclaim,
> > + * which is important when on a NUMA setup the allowed
> > + * zones are together not big enough to reach the
> > + * global limit. The proper fix for these situations
> > + * will require awareness of zones in the
> > + * dirty-throttling and the flusher threads.
> > + */
> > + if ((alloc_flags & ALLOC_WMARK_LOW) &&
> > + (gfp_mask & __GFP_WRITE) && !zone_dirty_ok(zone))
> > + goto this_zone_full;
> >
> > BUILD_BUG_ON(ALLOC_NO_WATERMARKS < NR_WMARK);
> > if (!(alloc_flags & ALLOC_NO_WATERMARKS)) {
>
> This wil call
>
> if (NUMA_BUILD)
> zlc_mark_zone_full(zonelist, z);
>
> And this zone will be marked as full.
>
> IIUC, zlc_clear_zones_full() is called only when direct reclaim ends.
> So, if no one calls direct-reclaim, 'full' mark may never be cleared
> even when number of dirty pages goes down to safe level ?
> I'm sorry if this is alread discussed.
It does not remember which zones are marked full for longer than a
second - see zlc_setup() - and also ignores this information when an
iteration over the zonelist with the cache enabled came up
empty-handed.
I thought it would make sense to take advantage of the cache and save
the zone_dirty_ok() checks against ineligible zones too on subsequent
iterations.
--
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>
next prev parent reply other threads:[~2011-11-24 13:12 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-23 13:34 [patch 0/5] mm: per-zone dirty limits v3-resend Johannes Weiner
2011-11-23 13:34 ` [patch 1/5] mm: exclude reserved pages from dirtyable memory Johannes Weiner
2011-11-30 0:20 ` Andrew Morton
2011-12-07 13:58 ` Johannes Weiner
2011-11-23 13:34 ` [patch 2/5] mm: writeback: cleanups in preparation for per-zone dirty limits Johannes Weiner
2011-11-23 13:34 ` [patch 3/5] mm: try to distribute dirty pages fairly across zones Johannes Weiner
2011-11-24 1:07 ` KAMEZAWA Hiroyuki
2011-11-24 13:11 ` Johannes Weiner [this message]
2011-11-25 1:00 ` KAMEZAWA Hiroyuki
2011-11-23 13:34 ` [patch 4/5] mm: filemap: pass __GFP_WRITE from grab_cache_page_write_begin() Johannes Weiner
2011-11-23 13:34 ` [patch 5/5] Btrfs: pass __GFP_WRITE for buffered write page allocations Johannes Weiner
-- strict thread matches above, loose matches on Subject: below --
2011-09-30 7:17 [patch 0/5] per-zone dirty limits v3 Johannes Weiner
2011-09-30 7:17 ` [patch 3/5] mm: try to distribute dirty pages fairly across zones Johannes Weiner
2011-09-30 7:35 ` Pekka Enberg
2011-09-30 8:55 ` Johannes Weiner
2011-09-30 14:28 ` Michal Hocko
2011-10-28 20:18 ` Wu Fengguang
2011-10-31 11:33 ` Wu Fengguang
2011-11-01 10:55 ` Johannes Weiner
[not found] ` <20111027155618.GA25524@localhost>
[not found] ` <20111027161359.GA1319@redhat.com>
[not found] ` <20111027204743.GA19343@localhost>
[not found] ` <20111027221258.GA22869@localhost>
[not found] ` <20111027231933.GB1319@redhat.com>
2011-10-28 20:39 ` Wu Fengguang
2011-11-01 10:52 ` Johannes Weiner
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=20111124131155.GB1225@cmpxchg.org \
--to=hannes@cmpxchg.org \
--cc=akpm@linux-foundation.org \
--cc=david@fromorbit.com \
--cc=fengguang.wu@intel.com \
--cc=hch@infradead.org \
--cc=jack@suse.cz \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@suse.de \
--cc=mhocko@suse.cz \
--cc=minchan.kim@gmail.com \
--cc=riel@redhat.com \
--cc=shaohua.li@intel.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