From: David Rientjes <rientjes@google.com>
To: Vlastimil Babka <vbabka@suse.cz>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Mel Gorman <mgorman@techsingularity.net>,
Michal Hocko <mhocko@suse.com>,
Joonsoo Kim <iamjoonsoo.kim@lge.com>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [patch 1/2] mm, zone: track number of pages in free area by migratetype
Date: Thu, 17 Nov 2016 14:11:27 -0800 (PST) [thread overview]
Message-ID: <alpine.DEB.2.10.1611171405210.99747@chino.kir.corp.google.com> (raw)
In-Reply-To: <49ed7412-eab7-4d8d-c6df-fdf76d98da4d@suse.cz>
On Thu, 17 Nov 2016, Vlastimil Babka wrote:
> > The total number of free pages is still tracked, however, to not make
> > zone_watermark_ok() more expensive. Reading /proc/pagetypeinfo, however,
> > is faster.
>
> Yeah I've already seen a case with /proc/pagetypeinfo causing soft
> lockups due to high number of iterations...
>
Thanks for taking a look at the patchset!
Wow, I haven't seen /proc/pagetypeinfo soft lockups yet, I thought this
was a relatively minor point :) But it looks like we need some
improvement in this behavior independent of memory compaction anyway.
> > This patch introduces no functional change and increases the amount of
> > per-zone metadata at worst by 48 bytes per memory zone (when CONFIG_CMA
> > and CONFIG_MEMORY_ISOLATION are enabled).
>
> Isn't it 48 bytes per zone and order?
>
Yes, sorry, I'll fix that in v2. I think less than half a kilobyte for
each memory zone is satisfactory for extra tracking, compaction
improvements, and optimized /proc/pagetypeinfo, though.
> > Signed-off-by: David Rientjes <rientjes@google.com>
>
> I'd be for this if there are no performance regressions. It affects hot
> paths and increases cache footprint. I think at least some allocator
> intensive microbenchmark should be used.
>
I can easily implement a test to stress movable page allocations from
fallback MIGRATE_UNMOVABLE pageblocks and freeing back to the same
pageblocks. I assume we're not interested in memory offline benchmarks.
What do you think about the logic presented in patch 2/2? Are you
comfortable with a hard-coded ratio such as 1/64th of free memory or would
you prefer to look at the zone's watermark with the number of free pages
from MIGRATE_MOVABLE pageblocks rather than NR_FREE_PAGES? I was split
between the two options.
--
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/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2016-11-17 22:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-17 1:32 David Rientjes
2016-11-17 1:32 ` [patch 2/2] mm, compaction: avoid async compaction if most free memory is ineligible David Rientjes
2016-11-17 17:04 ` [patch 1/2] mm, zone: track number of pages in free area by migratetype Vlastimil Babka
2016-11-17 22:11 ` David Rientjes [this message]
2016-11-18 20:58 ` Vlastimil Babka
2016-11-30 0:16 ` [patch v2 1/2] mm, zone: track number of movable free pages David Rientjes
2016-11-30 0:16 ` [patch v2 2/2] mm, compaction: avoid async compaction if most free memory is ineligible David Rientjes
2016-11-30 7:34 ` [patch v2 1/2] mm, zone: track number of movable free pages Vlastimil Babka
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=alpine.DEB.2.10.1611171405210.99747@chino.kir.corp.google.com \
--to=rientjes@google.com \
--cc=akpm@linux-foundation.org \
--cc=iamjoonsoo.kim@lge.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@techsingularity.net \
--cc=mhocko@suse.com \
--cc=vbabka@suse.cz \
/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