From: Matthew Wilcox <willy@infradead.org>
To: Alex Shi <alex.shi@linux.alibaba.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Hugh Dickins <hughd@google.com>,
Alexander Duyck <alexander.h.duyck@linux.intel.com>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [PATCH 2/2] mm/pageblock: remove false sharing in pageblock_flags
Date: Sun, 16 Aug 2020 05:17:20 +0100 [thread overview]
Message-ID: <20200816041720.GG17456@casper.infradead.org> (raw)
In-Reply-To: <1597549677-7480-2-git-send-email-alex.shi@linux.alibaba.com>
On Sun, Aug 16, 2020 at 11:47:57AM +0800, Alex Shi wrote:
> Current pageblock_flags is only 4 bits, so it has to share a char size
> in cmpxchg when get set, the false sharing cause perf drop.
>
> If we incrase the bits up to 8, false sharing would gone in cmpxchg. and
> the only cost is half char per pageblock, which is half char per 128MB
> on x86, 4 chars in 1 GB.
I don't believe this patch has that effect, mostly because it still does
cmpxchg() on words instead of bytes.
But which functions would benefit? It seems to me this cmpxchg() is
only called from the set_pageblock_migratetype() morass of functions,
none of which are called in hot paths as far as I can make out.
So are you just reasoning by analogy with the previous patch where you
have measured a performance improvement, or did you send the wrong patch,
or did I overlook a hot path that calls one of the pageblock migration
functions?
next prev parent reply other threads:[~2020-08-16 4:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-16 3:47 [PATCH 1/2] mm/pageblock: mitigation cmpxchg false sharing in pageblock flags Alex Shi
2020-08-16 3:47 ` [PATCH 2/2] mm/pageblock: remove false sharing in pageblock_flags Alex Shi
2020-08-16 4:17 ` Matthew Wilcox [this message]
2020-08-16 14:10 ` Alex Shi
2020-08-16 15:56 ` Alexander Duyck
2020-08-18 7:15 ` Alex Shi
2020-08-16 4:09 ` [PATCH 1/2] mm/pageblock: mitigation cmpxchg false sharing in pageblock flags Matthew Wilcox
2020-08-16 13:53 ` Alex Shi
2020-08-16 12:16 ` David Hildenbrand
2020-08-16 14:14 ` Alex Shi
2020-08-17 9:58 ` Wei Yang
2020-08-17 11:02 ` Alex Shi
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=20200816041720.GG17456@casper.infradead.org \
--to=willy@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=alex.shi@linux.alibaba.com \
--cc=alexander.h.duyck@linux.intel.com \
--cc=hughd@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
/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