From: dhylands@gmail.com (Dave Hylands)
To: kernelnewbies@lists.kernelnewbies.org
Subject: about 64-bits division in kernel
Date: Thu, 19 May 2011 23:47:03 -0700 [thread overview]
Message-ID: <BANLkTi=X_UcFB089nu9_DS6Gjd=GXJt=3A@mail.gmail.com> (raw)
In-Reply-To: <BANLkTimkyaqLJZ1C9_gtjsVcctUhhA+RrA@mail.gmail.com>
Hi loody,
On Thu, May 19, 2011 at 10:51 PM, loody <miloody@gmail.com> wrote:
> hi Dave:
> Thanks for your kind reply.
> 2011/5/20 Dave Hylands <dhylands@gmail.com>:
>> Hi lody,
>>
>> On Thu, May 19, 2011 at 8:34 PM, loody <miloody@gmail.com> wrote:
>>> hi all:
>>> My platform is 32-bits cpu and I need following calculation in my driver.
>>> #define longdiv(sr1, sr2, div) ? ? ?(unsigned long )((((unsigned long
>>> long)(sr1) << 32) ^ (sr2)) / (div))
>>>
>>> my question are:
>>> 1. why "__udivdi3" has any relationship with above calculation?
>>
>> Because you're doing 64 bit arithmetic (unsigned long long) and 64 bit
>> division is not supported in all kernels.
>
> why the name "__udivdi3" has relation to 64-bits arighmetic?
> Why linker ask for "__udivdi3", it seems there is a common sense for
> linker that when doing 64-bits calculation it will try to find
> "__udivdi3", am i right?
Well, since the CPU doesn't directly have support for 64-bit division,
the compiler uses helper functions. The helper function __udivdi3 is
the one for the particular operation you're providing.
The functions in question are part of a library called libgcc and this
library is not linked into the kernel.
>>> 2. I know the above calculation is implemented in clibc, but why
>>> kernel still implement itself?
>>> ? ? why kernel try to make another wheel instead of including what
>>> clib provided ?
>>
>> The kernel doesn't use anything from the C runtime ?library at all.
>>
>> 64-bit division and floating point are 2 things not supported in the
>> kernel, although they do happen to word on some platforms, they aren't
>> portable operations.
>>
> the 64-bit division seem supported in gcc toolchain, and gcc will take
> care the platform issue when we cross-compile the gcc, right?
> It should be safe to static link the 64bits division in gcc.
You need to use the do_div macro available in linux/div64.h to perform
64-bit division in the kernel.
--
Dave Hylands
Shuswap, BC, Canada
http://www.davehylands.com
next prev parent reply other threads:[~2011-05-20 6:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-20 3:34 about 64-bits division in kernel loody
2011-05-20 4:15 ` Dave Hylands
2011-05-20 5:51 ` loody
2011-05-20 6:47 ` Dave Hylands [this message]
2011-05-21 6:57 ` loody
2011-05-21 7:22 ` Dave Hylands
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='BANLkTi=X_UcFB089nu9_DS6Gjd=GXJt=3A@mail.gmail.com' \
--to=dhylands@gmail.com \
--cc=kernelnewbies@lists.kernelnewbies.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;
as well as URLs for NNTP newsgroup(s).