All of
 help / color / mirror / Atom feed
From: Johannes Weiner <>
To: Andrew Morton <>
Subject: Re: [patch 07/15] mm: memcontrol: fix excessive complexity in memory.stat reporting
Date: Fri, 12 Jan 2018 12:05:01 -0500	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

Sorry, this email slipped through the cracks.

On Wed, Dec 06, 2017 at 05:06:35PM -0800, Andrew Morton wrote:
> On Fri, 1 Dec 2017 13:57:50 +0000 Johannes Weiner <> wrote:
> > The memcg cpu_dead callback can be called early during startup
> > (CONFIG_DEBUG_HOTPLUG_CPU0) with preemption enabled, which triggers a
> > warning in its __this_cpu_xchg() calls. But CPU locality is always
> > guaranteed, which is the only thing we really care about here.
> > 
> > Using the preemption-safe this_cpu_xchg() addresses this problem.
> > 
> > Signed-off-by: Johannes Weiner <>
> > ---
> > 
> > Andrew, can you please merge this fixlet into the original patch?
> Did.
> I see that lkp-robot identified a performance regression and pointed
> the finger at this patch?

Right, it reports a perf drop in page fault stress tests, but that is
to be the expected trade-off. Before, we'd do everything per cpu, and
have to collapse all counters everytime somebody would read the stats.
Now we fold them in batches, which introduces a periodic atomic when
the batches are flushed (same frequency as we per-cpu cache charges
for the atomic page_counter).

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>

      reply	other threads:[~2018-01-12 17:04 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-30 22:15 akpm
2017-12-01 13:57 ` Johannes Weiner
2017-12-07  1:06   ` Andrew Morton
2018-01-12 17:05     ` Johannes Weiner [this message]

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 \ \ \ \ \ \ \
    --subject='Re: [patch 07/15] mm: memcontrol: fix excessive complexity in memory.stat reporting' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.