From: Benoit Boissinot <bboissin@gmail.com>
To: Soumyadip Das Mahapatra <kernelhacker@visualserver.org>
Cc: Akinobu Mita <akinobu.mita@gmail.com>,
Harvey Harrison <harvey.harrison@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] bitreversal program
Date: Wed, 21 May 2008 11:11:11 +0200 [thread overview]
Message-ID: <20080521091111.GU7567@pirzuine> (raw)
In-Reply-To: <Pine.LNX.4.64.0805211029250.1736@visualserver.org>
[-- Attachment #1: Type: text/plain, Size: 718 bytes --]
On Wed, May 21, 2008 at 10:54:15AM +0200, Soumyadip Das Mahapatra wrote:
> On Tue, 20 May 2008, Benoit Boissinot wrote:
>
> Sorry to disturb you again. But i tested my code against Akinobu's one
> and the test result shows my code takes less cpu time than that of
> Akinobu's.
>
> My processor is 1.4 GHz one.
> I am not forcing you to review my code( or i've no expectation of
> inclusion of it ) but its just a curiousity: what is truth behind
> the output.
I'm using a core duo 1.2GHz, if you want to play with the code, I'm
attaching a tarball (it's hackish, just change the #include at the top
of bitrev.h to switch implementation).
I'm using gcc -Wall -O3 to compile with gcc 4.2.3.
regards,
Benoit
--
:wq
[-- Attachment #2: bitrev.tar.bz2 --]
[-- Type: application/octet-stream, Size: 1520 bytes --]
next prev parent reply other threads:[~2008-05-21 9:11 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-19 17:04 [PATCH 1/2] bitreversal program 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
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 [this message]
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=20080521091111.GU7567@pirzuine \
--to=bboissin@gmail.com \
--cc=akinobu.mita@gmail.com \
--cc=harvey.harrison@gmail.com \
--cc=kernelhacker@visualserver.org \
--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 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.