From: "Fabio M. De Francesco" <fmdefrancesco@gmail.com>
To: Al Viro <viro@zeniv.linux.org.uk>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
ira.weiny@intel.com
Subject: Re: [git pull] common helper for kmap_local_page() users in local filesystems
Date: Mon, 27 Mar 2023 12:20:23 +0200 [thread overview]
Message-ID: <2729240.9PvXe5no7K@suse> (raw)
In-Reply-To: <8232398.NyiUUSuA9g@suse>
On sabato 11 marzo 2023 18:11:01 CEST Fabio M. De Francesco wrote:
> On venerdì 10 marzo 2023 21:44:31 CET Al Viro wrote:
> > kmap_local_page() conversions in local filesystems keep running into
> >
> > kunmap_local_page()+put_page() combinations; we can keep inventing names
> > for identical inline helpers, but it's getting rather inconvenient. I've
> > added a trivial helper to linux/highmem.h instead.
>
> Yeah, "put_and_unmap_page()". Nice helper :-)
[snip]
Hi Al,
> Why did you name it "put_and_unmap_page()" instead of
"unmap_and_put_page()",
> for we always unmap first _and_ put the page immediately the unmapping?
>
> It seems it want to imply that instead we put first and unmap later (which
> would be wrong). That name sounds misleading to me and not sound (logically
> speaking).
>
> Am I missing some obscure convention behind your choice of that name for the
> helper?
Can you please explain what I'm missing behind your motivation?
Thanks,
Fabio
P.S.: Adding Ira to the Cc list, since he's been doing kmap() and
kmap_atomic() conversions long time before I too started with them.
prev parent reply other threads:[~2023-03-27 10:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-10 20:44 [git pull] common helper for kmap_local_page() users in local filesystems Al Viro
2023-03-11 4:52 ` pr-tracker-bot
2023-03-11 17:11 ` Fabio M. De Francesco
2023-03-27 10:20 ` 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=2729240.9PvXe5no7K@suse \
--to=fmdefrancesco@gmail.com \
--cc=ira.weiny@intel.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=viro@zeniv.linux.org.uk \
/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).