From: Miklos Szeredi <miklos@szeredi.hu>
To: Hao Peng <flyingpenghao@gmail.com>
Cc: linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH v2] fuse: Use kmap_local_page()
Date: Wed, 8 Sep 2021 08:03:41 +0200 [thread overview]
Message-ID: <CAJfpegu=0AovQ064-iFX3D8s1WiAjvUfi1eYU6zzjQek0+nDbg@mail.gmail.com> (raw)
In-Reply-To: <CAPm50a+MKpDFSoNr9gtYRaE4FQgeihpvc6NDdcs8za8X1ZVQGQ@mail.gmail.com>
On Wed, 8 Sept 2021 at 04:03, Hao Peng <flyingpenghao@gmail.com> wrote:
>
> From : Peng Hao <flyingpeng@tencent.com>
>
> Due to the introduction of kmap_local_*, the storage of slots
> used for short-term mapping has changed from per-CPU to per-thread.
> kmap_atomic() disable preemption, while kmap_local_*() only disable
> migration.
> There is no need to disable preemption in several kamp_atomic
> places used in fuse.
> The detailed introduction of kmap_local_*d can be found here:
> https://lwn.net/Articles/836144/
Okay. The patch is still garbled. Please use git-send-email or some
other mail client.
Thanks,
Miklos
prev parent reply other threads:[~2021-09-08 6:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-08 2:03 [PATCH v2] fuse: Use kmap_local_page() Hao Peng
2021-09-08 6:03 ` Miklos Szeredi [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='CAJfpegu=0AovQ064-iFX3D8s1WiAjvUfi1eYU6zzjQek0+nDbg@mail.gmail.com' \
--to=miklos@szeredi.hu \
--cc=flyingpenghao@gmail.com \
--cc=linux-fsdevel@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.