archive mirror
 help / color / mirror / Atom feed
From: Mel Gorman <>
To: Kemi Wang <>
Cc: Andrew Morton <>,
	Michal Hocko <>,
	Johannes Weiner <>,
	Christopher Lameter <>,
	Dave <>,
	Andi Kleen <>,
	Jesper Dangaard Brouer <>,
	Ying Huang <>, Aaron Lu <>,
	Tim Chen <>, Linux MM <>,
	Linux Kernel <>
Subject: Re: [PATCH v2 0/3] Separate NUMA statistics from zone statistics
Date: Fri, 25 Aug 2017 09:04:37 +0100	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On Thu, Aug 24, 2017 at 05:59:58PM +0800, Kemi Wang wrote:
> Each page allocation updates a set of per-zone statistics with a call to
> zone_statistics(). As discussed in 2017 MM summit, these are a substantial
> source of overhead in the page allocator and are very rarely consumed. This
> significant overhead in cache bouncing caused by zone counters (NUMA
> associated counters) update in parallel in multi-threaded page allocation
> (pointed out by Dave Hansen).

For the series;

Acked-by: Mel Gorman <>

Mel Gorman

To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to  For more info on Linux MM,
see: .
Don't email: <a href=mailto:""> </a>

  parent reply	other threads:[~2017-08-25  8:04 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-24  9:59 [PATCH v2 0/3] Separate NUMA statistics from zone statistics Kemi Wang
2017-08-24  9:59 ` [PATCH v2 1/3] mm: Change the call sites of numa statistics items Kemi Wang
2017-08-24 10:00 ` [PATCH v2 2/3] mm: Update NUMA counter threshold size Kemi Wang
2017-08-24 10:00 ` [PATCH v2 3/3] mm: Consider the number in local CPUs when *reads* NUMA stats Kemi Wang
2017-08-25  8:04 ` Mel Gorman [this message]
2017-08-25 13:16   ` [PATCH v2 0/3] Separate NUMA statistics from zone statistics Jesper Dangaard Brouer

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \

* 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).