From: Andrew Morton <akpm@linux-foundation.org>
To: Johannes Weiner <hannes@cmpxchg.org>
Cc: linux-mm@kvack.org, mhocko@suse.com, vdavydov.dev@gmail.com
Subject: Re: [patch 07/15] mm: memcontrol: fix excessive complexity in memory.stat reporting
Date: Wed, 6 Dec 2017 17:06:35 -0800 [thread overview]
Message-ID: <20171206170635.e3e45c895750538ee9283033@linux-foundation.org> (raw)
In-Reply-To: <20171201135750.GB8097@cmpxchg.org>
On Fri, 1 Dec 2017 13:57:50 +0000 Johannes Weiner <hannes@cmpxchg.org> 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 <hannes@cmpxchg.org>
> ---
>
> 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?
--
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:[~2017-12-07 1:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-30 22:15 [patch 07/15] mm: memcontrol: fix excessive complexity in memory.stat reporting akpm
2017-12-01 13:57 ` Johannes Weiner
2017-12-07 1:06 ` Andrew Morton [this message]
2018-01-12 17:05 ` 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=20171206170635.e3e45c895750538ee9283033@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=hannes@cmpxchg.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.com \
--cc=vdavydov.dev@gmail.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 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.