From: Soumyadip Das Mahapatra <kernelhacker@visualserver.org>
To: Harvey Harrison <harvey.harrison@gmail.com>
Cc: linux-kernel@vger.kernel.org, akinobu.mita@gmail.com
Subject: Re: [PATCH 1/2] bitreversal program
Date: Tue, 20 May 2008 13:01:27 +0200 (CEST) [thread overview]
Message-ID: <Pine.LNX.4.64.0805201254240.18899@visualserver.org> (raw)
In-Reply-To: <1211229736.5915.86.camel@brick>
On Mon, 19 May 2008, Harvey Harrison wrote:
> On Mon, 2008-05-19 at 19:04 +0200, Soumyadip Das Mahapatra wrote:
>> --- a/include/linux/bitrev.h 2008-04-17 08:19:44.000000000 +0530
>> +++ b/include/linux/bitrev.h 2008-05-19 21:49:46.000000000 +0530
>> @@ -3,11 +3,32 @@
>>
>> #include <linux/types.h>
>>
>> -extern u8 const byte_rev_table[256];
>> +/**
>> + * Here is a generalised bit reversal program
>> + * @x: word to get bits reversed
>> + * @k: key, explained below
>> + * for k = 31, it reverses the bits of word(32 bit)
>> + * for k = 24, it reverses the bytes in word
>> + * for k = 7, it reverses the bits in every byte without
>> + * changing the positions of bytes in a word
>> + * and for k = 16 it swaps the left and right halves of a
>> + * word
>> + */
>>
>> -static inline u8 bitrev8(u8 byte)
>
> What about anybody who currently uses bitrev8?
>
>> +static inline u32 gen_bit_rev(u32 x, u32 k)
>> {
>> - return byte_rev_table[byte];
>> + if(k & 1)
>> + x = (x & 0x55555555) << 1 | (x & 0xaaaaaaaa) >> 1;
>> + if(k & 2)
>> + x = (x & 0x33333333) << 2 | (x & 0xcccccccc) >> 2;
>> + if(k & 4)
>> + x = (x & 0x0f0f0f0f) << 4 | (x & 0xf0f0f0f0) >> 4;
>> + if(k & 8)
>> + x = (x & 0x00ff00ff) << 8 | (x & 0xff00ff00) >> 8;
>> + if(k & 16)
>> + x = (x & 0x0000ffff) << 16 | (x & 0xffff0000) >> 16;
>> +
>> + return x;
>> }
>
> Why is this better than a single 256 byte table?
>
> Harvey
>
>
> --
> This message has been scanned for viruses and
> dangerous content by MailScanner, and is
> believed to be clean.
>
>
Thanks for reviewing Harvey :-)
please look at the line below
>> -static inline u8 bitrev8(u8 byte)
It is a static function, so you cant use it from outside of this
file. So there should not be anyone using this function.
>Why is this better than a single 256 byte table?
Why store those things if stuffs can be done in smoother and cleaner
(using less memeory ofcourse) way!
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
next prev parent reply other threads:[~2008-05-20 11:01 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-19 17:04 Soumyadip Das Mahapatra
2008-05-19 20:42 ` Harvey Harrison
2008-05-20 6:53 ` John Hubbard
2008-05-20 11:01 ` Soumyadip Das Mahapatra [this message]
2008-05-20 12:13 ` Akinobu Mita
2008-05-20 15:25 ` Soumyadip Das Mahapatra
2008-05-20 15:47 ` Benoit Boissinot
2008-05-20 15:57 ` Soumyadip Das Mahapatra
2008-05-20 16:39 ` Benoit Boissinot
2008-05-21 8:54 ` Soumyadip Das Mahapatra
2008-05-21 9:11 ` Benoit Boissinot
2008-05-21 11:11 ` Rene Herman
2008-05-21 16:52 ` Tilman Schmidt
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=Pine.LNX.4.64.0805201254240.18899@visualserver.org \
--to=kernelhacker@visualserver.org \
--cc=akinobu.mita@gmail.com \
--cc=harvey.harrison@gmail.com \
--cc=linux-kernel@vger.kernel.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
Powered by JetHome