From: Prathu Baronia <prathubaronia2011@gmail.com>
To: linux-kernel@vger.kernel.org
Cc: chintan.pandya@oneplus.com,
Prathu Baronia <prathu.baronia@oneplus.com>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>,
Vincenzo Frascino <vincenzo.frascino@arm.com>,
"glider@google.com" <glider@google.com>,
Geert Uytterhoeven <geert@linux-m68k.org>,
Andrew Morton <akpm@linux-foundation.org>,
Anshuman Khandual <anshuman.khandual@arm.com>,
Andrey Konovalov <andreyknvl@google.com>,
linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/1] mm: Optimizing hugepage zeroing in arm64
Date: Thu, 21 Jan 2021 22:21:50 +0530 [thread overview]
Message-ID: <20210121165153.17828-1-prathu.baronia@oneplus.com> (raw)
Hello!
This patch removes the unnecessary kmap calls in the hugepage zeroing path and
improves the timing by 62%.
I had proposed a similar change in Apr-May'20 timeframe in memory.c where I
proposed to clear out a hugepage by directly calling a memset over the whole
hugepage but got the opposition that the change was not architecturally neutral.
Upon revisiting this now I see significant improvement by removing around 2k
barrier calls from the zeroing path. So hereby I propose an arm64 specific
definition of clear_user_highpage().
Prathu Baronia (1):
mm: Optimizing hugepage zeroing in arm64
arch/arm64/include/asm/page.h | 3 +++
arch/arm64/mm/copypage.c | 8 ++++++++
2 files changed, 11 insertions(+)
--
2.17.1
next reply other threads:[~2021-01-21 16:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-21 16:51 Prathu Baronia [this message]
2021-01-21 16:51 ` [PATCH 1/1] mm: Optimizing hugepage zeroing in arm64 Prathu Baronia
2021-01-21 17:46 ` [PATCH 0/1] " Will Deacon
2021-01-21 18:59 ` Robin Murphy
2021-01-22 12:13 ` Catalin Marinas
2021-01-22 12:45 ` Robin Murphy
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=20210121165153.17828-1-prathu.baronia@oneplus.com \
--to=prathubaronia2011@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=andreyknvl@google.com \
--cc=anshuman.khandual@arm.com \
--cc=catalin.marinas@arm.com \
--cc=chintan.pandya@oneplus.com \
--cc=geert@linux-m68k.org \
--cc=glider@google.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=prathu.baronia@oneplus.com \
--cc=vincenzo.frascino@arm.com \
--cc=will@kernel.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;
as well as URLs for NNTP newsgroup(s).