All of lore.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: for.poige+linux@gmail.com
Cc: linux-raid@vger.kernel.org, neilb@suse.de
Subject: Re: raid6's using not the best bandwidth method && raid6 algo is significantly slower in x86_64.
Date: Sun, 16 Nov 2008 16:36:07 -0800	[thread overview]
Message-ID: <4920BC77.9010709@zytor.com> (raw)
In-Reply-To: <43d009740811160818v49c530b1r9e01b79c1d9dcfdd@mail.gmail.com>

Igor Podlesny wrote:
> 
> So, there're 2 strange things in those dmesgs. The first one might be
> unrelated to Linux RAID but affects it -- have you noticed that in
> x86_64, raid6 algorithm is ~ 50 % slower, than in x86_32? Is that due
> to not too optimized code for x86_64 mode? And the second -- why is
> raid6 using algorithm sse2x4 (3175 MB/s), whereas int64x2 gives
> slightly better (~ 15 %) throughput -- 3660 MB/s?
> 
> Has anyone on the list similar observations? Can gcc's version
> difference affect so much? I doubt that, but I can try build x86_32
> with gcc 4.3.1 (as x86_64 was).
> 

The SSE modes have nicer cache behaviours and are therefore preferred
even if they are slower.

It is very odd that your SSE2 modes are that much slower in 64-bit mode.
 It could just be an artifact of the may the test is done (cache
anomalies?), but I kind of suspect there is something more fishy going on.

The sse2 code in the x1 and x2 case is actually identical between x86-32
and -64 (the x4 case is only available for -64) so it is very strange
that you're seeing this kind of effect.

	-hpa

  reply	other threads:[~2008-11-17  0:36 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-16 16:18 raid6's using not the best bandwidth method && raid6 algo is significantly slower in x86_64 Igor Podlesny
2008-11-17  0:36 ` H. Peter Anvin [this message]
2008-11-17 20:56   ` Igor Podlesny
  -- strict thread matches above, loose matches on Subject: below --
2008-11-17 22:35 H. Peter Anvin
2008-11-18 12:03 ` Igor Podlesny
2008-11-18 15:47   ` H. Peter Anvin
2008-11-21 19:22     ` Igor Podlesny
2008-11-21 19:31       ` H. Peter Anvin
2008-11-21 19:33         ` Igor Podlesny
2008-11-21 20:15           ` H. Peter Anvin
2008-11-22  5:40             ` Igor Podlesny
2008-11-22  5:42               ` H. Peter Anvin
2008-11-22  5:45                 ` Igor Podlesny
2008-11-23  1:12                   ` John Robinson
2008-12-05 13:36                   ` Igor Podlesny
2008-12-05 17:34                     ` H. Peter Anvin

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=4920BC77.9010709@zytor.com \
    --to=hpa@zytor.com \
    --cc=for.poige+linux@gmail.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=neilb@suse.de \
    /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.