From: Andrew Morton <akpm@linux-foundation.org>
To: Jean Delvare <khali@linux-fr.org>
Cc: "Darrick J. Wong" <djwong@us.ibm.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
lm-sensors <lm-sensors@lm-sensors.org>
Subject: Re: [PATCH 1/2] Create a DIV_ROUND_CLOSEST macro to do division with rounding
Date: Tue, 11 Nov 2008 09:07:02 -0800 [thread overview]
Message-ID: <20081111090702.94be2a19.akpm@linux-foundation.org> (raw)
In-Reply-To: <20081111110454.073a6d94@hyperion.delvare>
On Tue, 11 Nov 2008 11:04:54 +0100 Jean Delvare <khali@linux-fr.org> wrote:
> Hi Darrick,
>
> On Mon, 10 Nov 2008 17:01:32 -0800, Darrick J. Wong wrote:
> >
> > Create a helper macro to divide two numbers and round the result to the
> > nearest whole number. This is a helper macro for hwmon drivers that
> > want to convert incoming sysfs values per standard hwmon practice, though
> > the macro itself can be used by anyone.
> >
> > Signed-off-by: Darrick J. Wong <djwong@us.ibm.com>
> > ---
> >
> > include/linux/kernel.h | 6 ++++++
> > 1 files changed, 6 insertions(+), 0 deletions(-)
> >
> > diff --git a/include/linux/kernel.h b/include/linux/kernel.h
> > index fba141d..fb02266 100644
> > --- a/include/linux/kernel.h
> > +++ b/include/linux/kernel.h
> > @@ -48,6 +48,12 @@ extern const char linux_proc_banner[];
> > #define FIELD_SIZEOF(t, f) (sizeof(((t*)0)->f))
> > #define DIV_ROUND_UP(n,d) (((n) + (d) - 1) / (d))
> > #define roundup(x, y) ((((x) + ((y) - 1)) / (y)) * (y))
> > +#define DIV_ROUND_CLOSEST(x, divisor)( \
> > +{ \
> > + typeof(divisor) __divisor = divisor; \
> > + (((x) + ((__divisor) / 2)) / (__divisor)); \
> > +} \
> > +)
> >
> > #define _RET_IP_ (unsigned long)__builtin_return_address(0)
> > #define _THIS_IP_ ({ __label__ __here; __here: (unsigned long)&&__here; })
> >
>
> I don't get why you implement this as a macro rather than an inline
> function? A function would look much better.
The idea is that DIV_ROUND_CLOSEST() can be used with arguments of any
size (char, short, ... long long) and will do all the suitable
promotion and will return a type of the appropriate width and
signedness.
It's not particularly pretty and can hide traps and pitfalls, but the
other way is tricky as well - it'd need a family of functions and
there's a risk that programmers will choose the wrong one.
next prev parent reply other threads:[~2008-11-11 17:08 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-11 1:01 [PATCH 1/2] Create a DIV_ROUND_CLOSEST macro to do division with rounding Darrick J. Wong
2008-11-11 1:01 ` [PATCH 2/2] adt74{62, 70, 73}: Use DIV_ROUND_CLOSEST for rounded division Darrick J. Wong
2008-11-11 10:04 ` [PATCH 1/2] Create a DIV_ROUND_CLOSEST macro to do division with rounding Jean Delvare
2008-11-11 17:07 ` Andrew Morton [this message]
2008-11-11 17:11 ` Jean Delvare
2008-11-11 18:51 ` Joe Perches
2008-11-11 23:05 ` [lm-sensors] " Trent Piepho
2008-11-11 23:20 ` Andrew Morton
2008-11-11 23:42 ` Trent Piepho
2008-11-12 0:08 ` Andrew Morton
2008-11-14 21:46 ` Trent Piepho
2008-11-14 22:24 ` Andrew Morton
2008-11-11 23:50 ` Jochen Voß
2009-08-03 11:57 ` Peter Zijlstra
2009-08-03 12:21 ` Jean Delvare
2009-08-03 12:27 ` Peter Zijlstra
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=20081111090702.94be2a19.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=djwong@us.ibm.com \
--cc=khali@linux-fr.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lm-sensors@lm-sensors.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