From: "Fabio M. De Francesco" <fmdefrancesco@gmail.com>
To: "Matthew Wilcox (Oracle)" <willy@infradead.org>,
Ira Weiny <ira.weiny@intel.com>, Jeff Layton <jlayton@kernel.org>,
Damien Le Moal <damien.lemoal@opensource.wdc.com>,
Andrew Morton <akpm@linux-foundation.org>,
Christian Brauner <brauner@kernel.org>,
Arnd Bergmann <arnd@arndb.de>, Jens Axboe <axboe@kernel.dk>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
Chaitanya Kulkarni <kch@nvidia.com>,
Kees Cook <keescook@chromium.org>,
Muchun Song <songmuchun@bytedance.com>,
Roman Gushchin <roman.gushchin@linux.dev>,
"Theodore Ts'o" <tytso@mit.edu>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: "Fabio M. De Francesco" <fmdefrancesco@gmail.com>
Subject: [RESEND PATCH 0/3] hfs: Replace kmap() with kmap_local_page()
Date: Sun, 21 Aug 2022 20:03:57 +0200 [thread overview]
Message-ID: <20220821180400.8198-1-fmdefrancesco@gmail.com> (raw)
kmap() is being deprecated in favor of kmap_local_page().
There are two main problems with kmap(): (1) It comes with an overhead as
mapping space is restricted and protected by a global lock for
synchronization and (2) it also requires global TLB invalidation when the
kmap’s pool wraps and it might block when the mapping space is fully
utilized until a slot becomes available.
With kmap_local_page() the mappings are per thread, CPU local, can take
page faults, and can be called from any context (including interrupts).
It is faster than kmap() in kernels with HIGHMEM enabled. Furthermore,
the tasks can be preempted and, when they are scheduled to run again, the
kernel virtual addresses are restored and still valid.
Since its use in fs/hfs is safe everywhere, it should be preferred.
Therefore, replace kmap() with kmap_local_page() in fs/hfs. Where
possible, use the suited standard helpers (memzero_page(), memcpy_page())
instead of open coding kmap_local_page() plus memset() or memcpy().
Fix a bug due to a page being not unmapped if the code jumps to the
"fail_page" label (1/3).
Tested in a QEMU/KVM x86_32 VM, 6GB RAM, booting a kernel with
HIGHMEM64GB enabled.
Few days ago Andrew requested a resend of this series. In the meantime
I'm also forwarding a "Reviewed-by" tag from Viacheslav Dubeyko.
Fabio M. De Francesco (3):
hfs: Unmap the page in the "fail_page" label
hfs: Replace kmap() with kmap_local_page() in bnode.c
hfs: Replace kmap() with kmap_local_page() in btree.c
fs/hfs/bnode.c | 32 ++++++++++++--------------------
fs/hfs/btree.c | 29 ++++++++++++++++-------------
2 files changed, 28 insertions(+), 33 deletions(-)
--
2.37.1
next reply other threads:[~2022-08-21 18:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-21 18:03 Fabio M. De Francesco [this message]
2022-08-21 18:03 ` [RESEND PATCH 1/3] hfs: Unmap the page in the "fail_page" label Fabio M. De Francesco
2022-08-21 18:03 ` [RESEND PATCH 2/3] hfs: Replace kmap() with kmap_local_page() in bnode.c Fabio M. De Francesco
2022-08-21 18:04 ` [RESEND PATCH 3/3] hfs: Replace kmap() with kmap_local_page() in btree.c Fabio M. De Francesco
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=20220821180400.8198-1-fmdefrancesco@gmail.com \
--to=fmdefrancesco@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=arnd@arndb.de \
--cc=axboe@kernel.dk \
--cc=brauner@kernel.org \
--cc=damien.lemoal@opensource.wdc.com \
--cc=ira.weiny@intel.com \
--cc=jlayton@kernel.org \
--cc=kch@nvidia.com \
--cc=keescook@chromium.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=roman.gushchin@linux.dev \
--cc=songmuchun@bytedance.com \
--cc=tytso@mit.edu \
--cc=willy@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).