public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
* AMD64 and RAID6
@ 2004-05-08 17:48 J. Ryan Earl
  2004-05-08 18:52 ` Jurriaan
  2004-05-11  2:13 ` H. Peter Anvin
  0 siblings, 2 replies; 3+ messages in thread
From: J. Ryan Earl @ 2004-05-08 17:48 UTC (permalink / raw)
  To: linux-kernel

I noticed the following in my dmesg:

raid5: measuring checksumming speed
  generic_sse:  6604.000 MB/sec
raid5: using function: generic_sse (6604.000 MB/sec)
raid6: int64x1   1847 MB/s
raid6: int64x2   2753 MB/s
raid6: int64x4   2878 MB/s
raid6: int64x8   1902 MB/s
raid6: sse2x1    1015 MB/s
raid6: sse2x2    1488 MB/s
raid6: sse2x4    1867 MB/s
raid6: using algorithm sse2x4 (1867 MB/s)
md: raid6 personality registered as nr 8
md: md driver 0.90.0 MAX_MD_DEVS=256, MD_SB_DISKS=27

Why doesn't RAID6 use the int64x4 algorithm in this situation?  What is 
the motivation of setting the 'prefer field' on the sse algorithms and 
not on the integer based algorithms?

 From drivers/md/raid6.h:
/* Routine choices */
struct raid6_calls {
        void (*gen_syndrome)(int, size_t, void **);
        int  (*valid)(void);    /* Returns 1 if this routine set is 
usable */
        const char *name;       /* Name of this routine set */
        int prefer;             /* Has special performance attribute */
};

-ryan

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: AMD64 and RAID6
  2004-05-08 17:48 AMD64 and RAID6 J. Ryan Earl
@ 2004-05-08 18:52 ` Jurriaan
  2004-05-11  2:13 ` H. Peter Anvin
  1 sibling, 0 replies; 3+ messages in thread
From: Jurriaan @ 2004-05-08 18:52 UTC (permalink / raw)
  To: J. Ryan Earl; +Cc: linux-kernel

From: J. Ryan Earl <heretic@clanhk.org>
Date: Sat, May 08, 2004 at 12:48:54PM -0500
> Why doesn't RAID6 use the int64x4 algorithm in this situation?  What is 
> the motivation of setting the 'prefer field' on the sse algorithms and 
> not on the integer based algorithms?
> 
IIRC, the sse variants have better cache-behaviour, and are thus almost
always selected.

Try googling for exact answers, this has come up before.

HTH,
Jurriaan
-- 
Spock: "Logic, logic, logic...  Logic is the beginning of wisdom,
Valeris, not  the end."
"STVI:TUC", Stardate 9522.6
Debian (Unstable) GNU/Linux 2.6.6-rc3-mm1 2x6062 bogomips 0.06 0.16

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: AMD64 and RAID6
  2004-05-08 17:48 AMD64 and RAID6 J. Ryan Earl
  2004-05-08 18:52 ` Jurriaan
@ 2004-05-11  2:13 ` H. Peter Anvin
  1 sibling, 0 replies; 3+ messages in thread
From: H. Peter Anvin @ 2004-05-11  2:13 UTC (permalink / raw)
  To: linux-kernel

Followup to:  <409D1D86.6050907@clanhk.org>
By author:    "J. Ryan Earl" <heretic@clanhk.org>
In newsgroup: linux.dev.kernel
>
> I noticed the following in my dmesg:
> 
> raid5: measuring checksumming speed
>   generic_sse:  6604.000 MB/sec
> raid5: using function: generic_sse (6604.000 MB/sec)
> raid6: int64x1   1847 MB/s
> raid6: int64x2   2753 MB/s
> raid6: int64x4   2878 MB/s
> raid6: int64x8   1902 MB/s
> raid6: sse2x1    1015 MB/s
> raid6: sse2x2    1488 MB/s
> raid6: sse2x4    1867 MB/s
> raid6: using algorithm sse2x4 (1867 MB/s)
> md: raid6 personality registered as nr 8
> md: md driver 0.90.0 MAX_MD_DEVS=256, MD_SB_DISKS=27
> 
> Why doesn't RAID6 use the int64x4 algorithm in this situation?  What is 
> the motivation of setting the 'prefer field' on the sse algorithms and 
> not on the integer based algorithms?
> 

The SSE algorithms are non-cache-polluting.  This makes them slightly
slower, but avoids slowing the rest of the machine down as much.

	-hpa

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2004-05-11  2:14 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2004-05-08 17:48 AMD64 and RAID6 J. Ryan Earl
2004-05-08 18:52 ` Jurriaan
2004-05-11  2:13 ` H. Peter Anvin

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox