From: minchan@kernel.org (Minchan Kim)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v1 0/3] arm: support get_user_pages_fast
Date: Mon, 17 Sep 2018 09:44:48 +0900 [thread overview]
Message-ID: <20180917004451.174527-1-minchan@kernel.org> (raw)
Recently, I got a report get_user_pages_fast helps app's launching time
due to reducing uninterruptible sleep time because it could reduce
mmap_sem lock contentions when app is launching.
To support gupf in ARM-non-LPAE, first patch reorders memory type table
to use 5th bit of the page table.
Second patch introduces L_PTE_SPECIAL for arm so that last patch can
support get_user_pags_fast.
I would greatly appreciate if guys review that I screw up something,
especially, architecture stuffs.
* from RFC
* Remove CPU_v7M - Catalin
* define DEV_NONSHARED to SHARED - Catalin
* https://lkml.kernel.org/r/20180910165011.zcighyuabshsmxjb at armageddon.cambridge.arm.com
Minchan Kim (3):
arm: mm: reordering memory type table
arm: mm: introduce L_PTE_SPECIAL
arm: mm: support get_user_pages_fast
arch/arm/Kconfig | 2 +-
arch/arm/include/asm/pgtable-2level.h | 22 ++-
arch/arm/include/asm/pgtable-3level.h | 6 -
arch/arm/include/asm/pgtable.h | 13 ++
arch/arm/mm/Makefile | 6 +
arch/arm/mm/gup.c | 221 ++++++++++++++++++++++++++
arch/arm/mm/proc-macros.S | 4 +-
7 files changed, 259 insertions(+), 15 deletions(-)
create mode 100644 arch/arm/mm/gup.c
--
2.19.0.397.gdd90340f6a-goog
next reply other threads:[~2018-09-17 0:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-17 0:44 Minchan Kim [this message]
2018-09-17 0:44 ` [PATCH v1 1/3] arm: mm: reordering memory type table Minchan Kim
2018-09-21 1:43 ` Minchan Kim
2018-09-24 16:22 ` Catalin Marinas
2018-09-28 6:34 ` Minchan Kim
2018-09-17 0:44 ` [PATCH v1 2/3] arm: mm: introduce L_PTE_SPECIAL Minchan Kim
2018-09-17 0:44 ` [PATCH v1 3/3] arm: mm: support get_user_pages_fast Minchan Kim
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=20180917004451.174527-1-minchan@kernel.org \
--to=minchan@kernel.org \
--cc=linux-arm-kernel@lists.infradead.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).