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
Subject: Re: raid6's using not the best bandwidth method && raid6 algo is significantly slower in x86_64.
Date: Fri, 21 Nov 2008 21:42:29 -0800	[thread overview]
Message-ID: <49279BC5.8080106@zytor.com> (raw)
In-Reply-To: <43d009740811212140l3ac2298ch512aca0e3631d269@mail.gmail.com>

Igor Podlesny wrote:
> 2008/11/22 H. Peter Anvin <hpa@zytor.com>:
> [...]
>> I just tested a version using gcc intrinsics with gcc 4.3, and it is
>> almost 20% faster than the inline assembly version.  That, plus the fact
>> that the code is actually readable, makes me really want to figure out
>> how best to deploy this.
> 
> 	Please let us know when commiting the patch -- 20 % is valuable. ;-)
> 

Looks like I was a bit too optimistic.  The 20% was because of the 
missed prefetchnta, which means polluting the cache.

	-hpa

  reply	other threads:[~2008-11-22  5:42 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-17 22:35 raid6's using not the best bandwidth method && raid6 algo is significantly slower in x86_64 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 [this message]
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
  -- strict thread matches above, loose matches on Subject: below --
2008-11-16 16:18 Igor Podlesny
2008-11-17  0:36 ` H. Peter Anvin
2008-11-17 20:56   ` Igor Podlesny

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=49279BC5.8080106@zytor.com \
    --to=hpa@zytor.com \
    --cc=for.poige+linux@gmail.com \
    --cc=linux-raid@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.