All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Fabio M. De Francesco" <fmdefrancesco@gmail.com>
To: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: Ira Weiny <ira.weiny@intel.com>
Subject: Re: [PATCH] hfsplus: Convert kmap() to kmap_local_page() in bnode.c
Date: Mon, 01 Aug 2022 15:23:41 +0200	[thread overview]
Message-ID: <3688658.kQq0lBPeGt@opensuse> (raw)
In-Reply-To: <20220720154324.8272-1-fmdefrancesco@gmail.com>

On mercoledì 20 luglio 2022 17:43:24 CEST Fabio M. De Francesco wrote:
> kmap() is being deprecated in favor of kmap_local_page().
> 
> 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 bnode.c is safe everywhere, it should be preferred.
> 
> Therefore, replace kmap() with kmap_local_page() in bnode.c. Where
> possible, use the suited standard helpers (memzero_page(), memcpy_page())
> instead of open coding kmap_local_page() plus memset() or memcpy().
> 
> Suggested-by: Ira Weiny <ira.weiny@intel.com>
> Signed-off-by: Fabio M. De Francesco <fmdefrancesco@gmail.com>
> ---
>  fs/hfsplus/bnode.c | 105 +++++++++++++++++++++------------------------
>  1 file changed, 48 insertions(+), 57 deletions(-)

Please drop this patch because I'll send it again in a series of three, one 
per file (bnode.c, bitmap.c, btree.c).

Unfortunately, while working at the last patch (btree.c), I just noticed 
that I had missed one of the call sites of kmap() in bitmap.c.

Therefore, I'd prefer to send that again in a patchset and find a way to 
test each of the three of them on a QEMU/KVM x86_32 VM, booting a kernel 
with HIGHMEM64GB enabled.

Thanks,

Fabio




      parent reply	other threads:[~2022-08-01 13:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-20 15:43 [PATCH] hfsplus: Convert kmap() to kmap_local_page() in bnode.c Fabio M. De Francesco
2022-07-22 17:43 ` Viacheslav Dubeyko
2022-08-01 13:23 ` Fabio M. De Francesco [this message]

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=3688658.kQq0lBPeGt@opensuse \
    --to=fmdefrancesco@gmail.com \
    --cc=ira.weiny@intel.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.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 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.