From: "Fabio M. De Francesco" <fmdefrancesco@gmail.com>
To: David Sterba <dsterba@suse.com>,
Andrew Morton <akpm@linux-foundation.org>
Cc: Ira Weiny <ira.weiny@intel.com>,
dsterba@suse.cz, Chris Mason <clm@fb.com>,
Josef Bacik <josef@toxicpanda.com>,
Nick Terrell <terrelln@fb.com>,
linux-btrfs@vger.kernel.org, linux-kernel@vger.kernel.org,
Filipe Manana <fdmanana@kernel.org>
Subject: Re: [PATCH] btrfs: Replace kmap() with kmap_local_page() in zstd.c
Date: Wed, 15 Jun 2022 07:29:55 +0200 [thread overview]
Message-ID: <3619537.MHq7AAxBmi@opensuse> (raw)
In-Reply-To: <YqjAVq+1PIpVIr0p@iweiny-desk3>
On martedì 14 giugno 2022 19:07:34 CEST Ira Weiny wrote:
> On Tue, Jun 14, 2022 at 06:28:48PM +0200, Fabio M. De Francesco wrote:
> > On martedì 14 giugno 2022 16:25:21 CEST David Sterba wrote:
> > > On Tue, Jun 14, 2022 at 01:22:50AM +0200, Fabio M. De Francesco
wrote:
> > > > On lunedì 13 giugno 2022 20:39:13 CEST David Sterba wrote:
> > > > > On Sat, Jun 11, 2022 at 03:52:03PM +0200, Fabio M. De Francesco
> > >
>
> [snip]
>
> > > > A better solution is changing the prototype of __kunmap_local(); I
> > > > suppose that Andrew won't object, but who knows?
> > > >
> > > > (+Cc Andrew Morton).
> > > >
> > > > I was waiting for your comments. At now I've done about 15
conversions
> > > > across the kernel but it's the first time I had to pass a pointer
to
> > const
> > > > void to kunmap_local(). Therefore, I was not sure if changing the
API
> > were
> > > > better suited (however I have already discussed this with Ira).
> > >
> > > IMHO it should be fixed in the API.
> > >
> > I agree with you in full.
> >
> > At the same time when you sent this email I submitted a patch to change
> > kunmap_local() and kunmap_atomic().
> >
> > After Andrew takes them I'll send v2 of this patch to zstd.c without
those
> > unnecessary casts.
>
> David,
>
> Would you be willing to take this through your tree as a pre-patch to the
kmap
> changes in btrfs?
>
> That would be easier for Fabio and probably you and Andrew in the long
run.
>
> Ira
David,
Please drop the first version of the changes[1] to the API and instead take
my second version.[2] I've only reworked the commit message (and subject,
but this was involuntary) to make explicit that the fundamental reason
behind these changes are semantic correctness.
Thanks,
Fabio
[1] https://lore.kernel.org/lkml/20220614142531.16478-1-fmdefrancesco@gmail.com/
[2] https://lore.kernel.org/lkml/20220615051256.31466-1-fmdefrancesco@gmail.com/
next prev parent reply other threads:[~2022-06-15 5:30 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-11 13:52 [PATCH] btrfs: Replace kmap() with kmap_local_page() in zstd.c Fabio M. De Francesco
2022-06-13 18:39 ` David Sterba
2022-06-13 23:22 ` Fabio M. De Francesco
2022-06-13 23:42 ` Fabio M. De Francesco
2022-06-14 14:25 ` David Sterba
2022-06-14 16:28 ` Fabio M. De Francesco
2022-06-14 17:07 ` Ira Weiny
2022-06-15 5:29 ` Fabio M. De Francesco [this message]
2022-06-15 13:27 ` David Sterba
2022-06-15 13:32 ` David Sterba
2022-07-14 0:25 ` Wang Yugui
2022-07-14 7:46 ` Fabio M. De Francesco
2022-07-14 12:33 ` David Sterba
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=3619537.MHq7AAxBmi@opensuse \
--to=fmdefrancesco@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=clm@fb.com \
--cc=dsterba@suse.com \
--cc=dsterba@suse.cz \
--cc=fdmanana@kernel.org \
--cc=ira.weiny@intel.com \
--cc=josef@toxicpanda.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=terrelln@fb.com \
/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.