From: Jean Delvare <khali@linux-fr.org>
To: Peter Zijlstra <peterz@infradead.org>
Cc: "Darrick J. Wong" <djwong@us.ibm.com>,
Andrew Morton <akpm@linux-foundation.org>,
linux-kernel <linux-kernel@vger.kernel.org>,
lm-sensors <lm-sensors@lm-sensors.org>,
Julia Lawall <julia@diku.dk>
Subject: Re: [PATCH 1/2] Create a DIV_ROUND_CLOSEST macro to do division with rounding
Date: Mon, 3 Aug 2009 14:21:38 +0200 [thread overview]
Message-ID: <20090803142138.51738a18@hyperion.delvare> (raw)
In-Reply-To: <1249300672.7924.53.camel@twins>
Hi Peter,
On Mon, 03 Aug 2009 13:57:52 +0200, Peter Zijlstra wrote:
> On Mon, 2008-11-10 at 17:01 -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.
>
> Its too late to rename this now isn't it :-/
We can always rename things, but it is costly, so we only do that if we
have a good reason (e.g. the original name caused confusion.)
>
> DIV_ROUND_{UP,CEIL}
> DIV_ROUND_{DOWN,FLOOR}
The latter is the simple integer division, so there is no point in
defining a macro for it. The former we already have.
>
> I get.
>
> The proposed thing is simply DIV_ROUND, but this DIV_ROUND_CLOSEST name
> is just wonky.
I can't disagree. I even think I argued about it back then, but then
finally gave up. You should have participated in the debate when it was
hot rather than 8 months later :(
>
> Also, shouldn't it be something like ?
>
> DIV_ROUND(x, y) (((x) + (((y)+1)/2)) / (y))
No, that wouldn't work. Simple example, 10/3 is 3.33. (10+3/2)/3 is 3
which is the correct rounded value. (10+(3+1)/2)/3 is 4 which is not
the correct rounded value.
> Also, do we want the default rounding to be symmetric or asymmetric?
I don't think we care at all. This macro will rarely be called on
negative numbers, and even then...
>
> I think round to half even or something would be nice, but would add an
> extra conditional, not sure its worth it (round away from zero only
> works for signed numbers and it would also cost one conditional).
Definitely not worth the extra cost. We do the rounding because it is
not too expensive and adds value. Fine-tuning it will cost more than is
worth, plus would lead to endless debates about what is the best
rounding strategy.
If anyone really needs additional control on rounding, they better do
not rely on a general helper, but instead implement their own rounding
function.
--
Jean Delvare
next prev parent reply other threads:[~2009-08-03 12:21 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
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 [this message]
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=20090803142138.51738a18@hyperion.delvare \
--to=khali@linux-fr.org \
--cc=akpm@linux-foundation.org \
--cc=djwong@us.ibm.com \
--cc=julia@diku.dk \
--cc=linux-kernel@vger.kernel.org \
--cc=lm-sensors@lm-sensors.org \
--cc=peterz@infradead.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