From: Mitchel Humpherys <mitchelh-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
To: Arnd Bergmann <arnd-r2nGTMty4D4@public.gmane.org>
Cc: Will Deacon <will.deacon-5wv7dgnIgG8@public.gmane.org>,
iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org,
Thierry Reding
<thierry.reding-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
Matt Wagantall <mattw-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>,
linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org
Subject: Re: [PATCH v4 1/2] iopoll: Introduce memory-mapped IO polling macros
Date: Fri, 10 Oct 2014 13:24:18 -0700 [thread overview]
Message-ID: <vnkwegufn05p.fsf@mitchelh-linux.qualcomm.com> (raw)
In-Reply-To: <1922221.DKAGMVXrIn@wuerfel> (Arnd Bergmann's message of "Fri, 10 Oct 2014 21:50:23 +0200")
On Fri, Oct 10 2014 at 12:50:23 PM, Arnd Bergmann <arnd-r2nGTMty4D4@public.gmane.org> wrote:
> On Friday 10 October 2014 12:44:45 Mitchel Humpherys wrote:
>> >> Regarding the division, for the overwhelmingly common case where the
>> >> user of the API passes in a constant for sleep_us the compiler optimizes
>> >> out this calculation altogether and just sticks the final result in (I
>> >> verified this with gcc 4.9 and the kernel build system's built-in
>> >> support for generating .s files). Conveying semantic meaning by using
>> >> `DIV_ROUND_UP' is nice but if you feel strongly about it we can make
>> >> this a shift instead.
>> >
>> > The more important question is probably if you want to keep the _ROUND_UP
>> > part. If that's not significant, I think a shift would be better.
>>
>> If we drop the _ROUND_UP then passing a sleep_us <= 4 would result in a
>> minimum sleep time of 0, so we'd be polling a lot faster than the user
>> had expected.
>
> How about changing the semantics to sleep at least the sleep_us time,
> and at most four times that? This would turn the expensive division into
> a multiplication and avoid the need for rounding.
We already have a bunch of code using this and I'm not sure what the
effect would be on the system by changing this. It would probably be
negligible but saving a couple of instructions hardly seems like
justification for a change... More importantly, I think users would
rather poll their register a little quicker than they asked, rather than
slower.
> If there are important reasons to keep doing the division, you could
> instead use '(sleep_us >> 4) + 1', which is also very cheap to compute
> and avoids the problem you mention.
But I think you meant `(sleep_us >> 2) + 1', right? Incidentally, that
illustrates the benefit of the semantic clarity provided by explicitly
dividing :). In any case, I'm happy to go with a shift here for v6.
-Mitch
--
Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum,
a Linux Foundation Collaborative Project
WARNING: multiple messages have this Message-ID (diff)
From: mitchelh@codeaurora.org (Mitchel Humpherys)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4 1/2] iopoll: Introduce memory-mapped IO polling macros
Date: Fri, 10 Oct 2014 13:24:18 -0700 [thread overview]
Message-ID: <vnkwegufn05p.fsf@mitchelh-linux.qualcomm.com> (raw)
In-Reply-To: <1922221.DKAGMVXrIn@wuerfel> (Arnd Bergmann's message of "Fri, 10 Oct 2014 21:50:23 +0200")
On Fri, Oct 10 2014 at 12:50:23 PM, Arnd Bergmann <arnd@arndb.de> wrote:
> On Friday 10 October 2014 12:44:45 Mitchel Humpherys wrote:
>> >> Regarding the division, for the overwhelmingly common case where the
>> >> user of the API passes in a constant for sleep_us the compiler optimizes
>> >> out this calculation altogether and just sticks the final result in (I
>> >> verified this with gcc 4.9 and the kernel build system's built-in
>> >> support for generating .s files). Conveying semantic meaning by using
>> >> `DIV_ROUND_UP' is nice but if you feel strongly about it we can make
>> >> this a shift instead.
>> >
>> > The more important question is probably if you want to keep the _ROUND_UP
>> > part. If that's not significant, I think a shift would be better.
>>
>> If we drop the _ROUND_UP then passing a sleep_us <= 4 would result in a
>> minimum sleep time of 0, so we'd be polling a lot faster than the user
>> had expected.
>
> How about changing the semantics to sleep at least the sleep_us time,
> and at most four times that? This would turn the expensive division into
> a multiplication and avoid the need for rounding.
We already have a bunch of code using this and I'm not sure what the
effect would be on the system by changing this. It would probably be
negligible but saving a couple of instructions hardly seems like
justification for a change... More importantly, I think users would
rather poll their register a little quicker than they asked, rather than
slower.
> If there are important reasons to keep doing the division, you could
> instead use '(sleep_us >> 4) + 1', which is also very cheap to compute
> and avoids the problem you mention.
But I think you meant `(sleep_us >> 2) + 1', right? Incidentally, that
illustrates the benefit of the semantic clarity provided by explicitly
dividing :). In any case, I'm happy to go with a shift here for v6.
-Mitch
--
Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum,
a Linux Foundation Collaborative Project
next prev parent reply other threads:[~2014-10-10 20:24 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-01 1:28 [PATCH v4 0/2] iommu/arm-smmu: hard iova_to_phys Mitchel Humpherys
2014-10-01 1:28 ` Mitchel Humpherys
[not found] ` <1412126893-15796-1-git-send-email-mitchelh-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
2014-10-01 1:28 ` [PATCH v4 1/2] iopoll: Introduce memory-mapped IO polling macros Mitchel Humpherys
2014-10-01 1:28 ` Mitchel Humpherys
[not found] ` <1412126893-15796-2-git-send-email-mitchelh-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
2014-10-01 8:25 ` Arnd Bergmann
2014-10-01 8:25 ` Arnd Bergmann
2014-10-08 1:47 ` Mitchel Humpherys
2014-10-08 1:47 ` Mitchel Humpherys
[not found] ` <vnkwoatngwmo.fsf-Yf+dfxj6toJBVvN7MMdr1KRtKmQZhJ7pQQ4Iyu8u01E@public.gmane.org>
2014-10-08 13:40 ` Arnd Bergmann
2014-10-08 13:40 ` Arnd Bergmann
2014-10-10 19:44 ` Mitchel Humpherys
2014-10-10 19:44 ` Mitchel Humpherys
[not found] ` <vnkwoatjn1zm.fsf-Yf+dfxj6toJBVvN7MMdr1KRtKmQZhJ7pQQ4Iyu8u01E@public.gmane.org>
2014-10-10 19:50 ` Arnd Bergmann
2014-10-10 19:50 ` Arnd Bergmann
2014-10-10 20:24 ` Mitchel Humpherys [this message]
2014-10-10 20:24 ` Mitchel Humpherys
2014-10-09 22:45 ` Mitchel Humpherys
2014-10-09 22:45 ` Mitchel Humpherys
2014-10-01 1:28 ` [PATCH v4 2/2] iommu/arm-smmu: add support for iova_to_phys through ATS1PR Mitchel Humpherys
2014-10-01 1:28 ` Mitchel Humpherys
[not found] ` <1412126893-15796-3-git-send-email-mitchelh-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
2014-10-01 8:27 ` Arnd Bergmann
2014-10-01 8:27 ` Arnd Bergmann
2014-10-01 19:52 ` Mitchel Humpherys
2014-10-01 19:52 ` Mitchel Humpherys
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=vnkwegufn05p.fsf@mitchelh-linux.qualcomm.com \
--to=mitchelh-sgv2jx0feol9jmxxk+q4oq@public.gmane.org \
--cc=arnd-r2nGTMty4D4@public.gmane.org \
--cc=iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=mattw-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org \
--cc=thierry.reding-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=will.deacon-5wv7dgnIgG8@public.gmane.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 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.