From: Dave Chinner <david@fromorbit.com>
To: Christophe Leroy <christophe.leroy@csgroup.eu>
Cc: Wu Bo <wubo40@huawei.com>,
linfeilong@huawei.com, linux-kernel@vger.kernel.org,
linux-crypto@vger.kernel.org, linux-fsdevel@vger.kernel.org,
davem@davemloft.net, herbert@gondor.apana.org.au,
viro@zeniv.linux.org.uk
Subject: Re: [PATCH 1/2] crypto: af_alg - use DIV_ROUND_UP helper macro for calculations
Date: Wed, 26 May 2021 18:31:37 +1000 [thread overview]
Message-ID: <20210526083137.GK2817@dread.disaster.area> (raw)
In-Reply-To: <20210525103744.Horde.nmFFeC3J2_-Qdu7udOYa8g1@messagerie.c-s.fr>
On Tue, May 25, 2021 at 10:37:44AM +0200, Christophe Leroy wrote:
> Wu Bo <wubo40@huawei.com> a écrit :
>
> > From: Wu Bo <wubo40@huawei.com>
> >
> > Replace open coded divisor calculations with the DIV_ROUND_UP kernel
> > macro for better readability.
> >
> > Signed-off-by: Wu Bo <wubo40@huawei.com>
> > ---
> > crypto/af_alg.c | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/crypto/af_alg.c b/crypto/af_alg.c
> > index 18cc82d..8bd288d 100644
> > --- a/crypto/af_alg.c
> > +++ b/crypto/af_alg.c
> > @@ -411,7 +411,7 @@ int af_alg_make_sg(struct af_alg_sgl *sgl, struct
> > iov_iter *iter, int len)
> > if (n < 0)
> > return n;
> >
> > - npages = (off + n + PAGE_SIZE - 1) >> PAGE_SHIFT;
> > + npages = DIV_ROUND_UP(off + n, PAGE_SIZE);
>
> You should use PFN_UP()
No. We are not using pfns here - we're converting a byte count to a
page count.
Besides, "PFN_UP" is a horrible, awful api. It does not decribe what
it does and anyone who is not a mm developer will look at it and ask
"what <the ....> does this do?" and have to go looking for it's
definition to determine what it does. Yes, that's exactyl what I've
just done, and I really wish I didn't because, well, it just
reinforces how much we suck at APIs...
OTOH, what DIV_ROUND_UP() does is obvious, widely understood, self
documenting and easy to determine if the usage is correct, which
indeed this is.
The lesson: do not use whacky obscure, out of context macros when a
simple, obvious, widely known macro will give the same result and
make the code easier to understand.
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
next prev parent reply other threads:[~2021-05-26 8:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-25 8:15 [PATCH 0/2] use DIV_ROUND_UP helper macro for calculations Wu Bo
2021-05-25 8:15 ` [PATCH 1/2] crypto: af_alg - " Wu Bo
2021-05-25 8:37 ` Christophe Leroy
2021-05-26 8:31 ` Dave Chinner [this message]
2021-06-03 12:30 ` Herbert Xu
2021-05-25 8:15 ` [PATCH 2/2] fs: direct-io: " Wu Bo
2021-05-25 8:38 ` Christophe Leroy
2021-05-25 8:41 ` [PATCH 0/2] " Christophe Leroy
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=20210526083137.GK2817@dread.disaster.area \
--to=david@fromorbit.com \
--cc=christophe.leroy@csgroup.eu \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=linfeilong@huawei.com \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
--cc=wubo40@huawei.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox