From: Fabio M. De Francesco <fmdefrancesco@gmail.com>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] [PATCH v3] intel: igb: igb_ethtool.c: Convert kmap() to kmap_local_page()
Date: Sat, 16 Apr 2022 18:28:12 +0200 [thread overview]
Message-ID: <2114356.Mh6RI2rZIc@leap> (raw)
In-Reply-To: <1897617.PYKUYFuaPT@leap>
On sabato 16 aprile 2022 17:52:20 CEST Fabio M. De Francesco wrote:
> On sabato 16 aprile 2022 16:09:58 CEST Julia Lawall wrote:
> >
> > On Sat, 16 Apr 2022, Alaa Mohamed wrote:
> >
> > >
> > > On ????/??/??? ???? ????:????, Julia Lawall wrote:
> > > >
> > > > On Sat, 16 Apr 2022, Alaa Mohamed wrote:
> > > >
> > > > > Convert kmap() to kmap_local_page()
> > > > >
> > > > > With kmap_local_page(), the mapping is per thread, CPU local and
> not
> > > > > globally visible.
> > > > It's not clearer.
> > > I mean this " fix kunmap_local path value to take address of the
mapped
> page"
> > > be more clearer
> > > > This is a general statement about the function. You
> > > > need to explain why it is appropriate to use it here. Unless it is
> the
> > > > case that all calls to kmap should be converted to call
> kmap_local_page.
> > > It's required to convert all calls kmap to kmap_local_page. So, I
don't
> what
> > > should the commit message be?
> >
> > If all calls should be changed then you can also say that.
>
> If all calls should be changed with no regards to the surrounding
contexts
> and special situations, we can just make an automated s/kmap()/
> kmap_local_page()/ or something else similar :)
Obviously, I was just kidding because we cannot massively and blindly
change all kmap() calls to kmap_local_page().
IMO, here the changes in code are good but Julia's objections are
legitimate too.
Thanks,
Fabio
> >
> > I thought that a previous commit on the outreachy list made some
> arguments
> > about how the affacted value was just allocated and thus could not yet
be
> > shared.
> >
> > julia
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osuosl.org/pipermail/intel-wired-lan/attachments/20220416/51c29e10/attachment-0001.html>
next prev parent reply other threads:[~2022-04-16 16:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-16 11:14 [Intel-wired-lan] [PATCH v3] intel: igb: igb_ethtool.c: Convert kmap() to kmap_local_page() Alaa Mohamed
2022-04-16 11:31 ` Julia Lawall
2022-04-16 13:14 ` Alaa Mohamed
2022-04-18 22:19 ` Ira Weiny
2022-04-19 13:37 ` Alaa Mohamed
2022-04-16 13:18 ` Alaa Mohamed
2022-04-16 14:09 ` Julia Lawall
2022-04-16 15:52 ` Fabio M. De Francesco
2022-04-16 16:28 ` Fabio M. De Francesco [this message]
2022-04-16 21:43 ` 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=2114356.Mh6RI2rZIc@leap \
--to=fmdefrancesco@gmail.com \
--cc=intel-wired-lan@osuosl.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