From: Heinrich Schuchardt <xypron.glpk@gmx.de>
To: OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>,
Alexander Kuleshov <kuleshovmail@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] fs/fat: calculate checksum in a loop instead of directly calculating
Date: Mon, 23 Feb 2015 21:40:59 +0100 [thread overview]
Message-ID: <54EB905B.8010704@gmx.de> (raw)
In-Reply-To: <87wq3fnep7.fsf@mail.parknet.co.jp>
On 18.02.2015 21:32, OGAWA Hirofumi wrote:
> Alexander Kuleshov <kuleshovmail@gmail.com> writes:
>
>> time ./test_with_loop
>>
>> real 0m0.001s
>> user 0m0.000s
>> sys 0m0.001s
>>
>> And
>>
>> time ./test_direct_calculation:
>>
>> real 0m0.002s
>> user 0m0.000s
>> sys 0m0.001s
>
> Hm,
>
> #include <stdio.h>
> #include <stdlib.h>
> #include <unistd.h>
>
> typedef unsigned char __u8;
> typedef unsigned char u8;
>
> #if 1
> static inline unsigned char fat_checksum(const __u8 *name)
> {
> unsigned char s = name[0];
> s = (s<<7) + (s>>1) + name[1]; s = (s<<7) + (s>>1) + name[2];
> s = (s<<7) + (s>>1) + name[3]; s = (s<<7) + (s>>1) + name[4];
> s = (s<<7) + (s>>1) + name[5]; s = (s<<7) + (s>>1) + name[6];
> s = (s<<7) + (s>>1) + name[7]; s = (s<<7) + (s>>1) + name[8];
> s = (s<<7) + (s>>1) + name[9]; s = (s<<7) + (s>>1) + name[10];
> return s;
> }
> #else
> static inline unsigned char fat_checksum(const __u8 *name)
> {
> unsigned char s = name[0];
> u8 i;
> for (i = 1; i < 11; i++)
> s = (s << 7) + (s >> 1) + name[i];
> return s;
> }
> #endif
>
> static __attribute__ ((noinline)) int test(unsigned char *name)
You have to put
__attribute__((optimize("unroll-loops")))
here to unroll the loop inside the function:
static __attribute__ ((noinline))
__attribute__((optimize("unroll-loops")))
int test(unsigned char *name)
> {
> long i;
> for (i = 0; i < 100000000L; i++)
> name[i % 11] = fat_checksum(name);
> return name[0];
> }
>
> int main(int argc, char *argv[])
> {
> printf("%u\n", test((unsigned char *)argv[1]));
> return 0;
> }
>
>
> $ gcc --version
> gcc (Debian 4.9.1-19) 4.9.1
> Copyright (C) 2014 Free Software Foundation, Inc.
> This is free software; see the source for copying conditions. There is NO
> warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
>
> $ gcc -O2 -o c.inline c.c
> # change #if 1 => #if 0
> $ gcc -O2 -o c.loop c.c
>
> $ time ./c.inline aaaaaaaaaaa
> 14
>
> real 0m0.550s
> user 0m0.548s
> sys 0m0.000s
> $ time ./c.loop aaaaaaaaaaa
> 14
>
> real 0m0.901s
> user 0m0.896s
> sys 0m0.004s
>
> This is my environment only? (gcc (Debian 4.9.1-19) 4.9.1)
>
$ time ./c.inline aaaaaaaaaaa
14
real 0m0.743s
user 0m0.740s
sys 0m0.000s
Without __attribute__((optimize("unroll-loops"))) :
$ time ./c.loop aaaaaaaaaaa
14
real 0m1.482s
user 0m1.472s
sys 0m0.004s
With __attribute__((optimize("unroll-loops"))) :
$ time ./c.loop aaaaaaaaaaa
14
real 0m0.742s
user 0m0.740s
sys 0m0.000s
Best regards
Heinrich Schuchardt
next prev parent reply other threads:[~2015-02-23 20:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-18 18:48 [PATCH] fs/fat: calculate checksum in a loop instead of directly calculating Alexander Kuleshov
2015-02-18 19:25 ` OGAWA Hirofumi
2015-02-18 19:46 ` Alexander Kuleshov
2015-02-18 20:32 ` OGAWA Hirofumi
2015-02-23 20:40 ` Heinrich Schuchardt [this message]
2015-02-24 2:42 ` OGAWA Hirofumi
2015-02-24 19:22 ` Heinrich Schuchardt
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=54EB905B.8010704@gmx.de \
--to=xypron.glpk@gmx.de \
--cc=hirofumi@mail.parknet.co.jp \
--cc=kuleshovmail@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