All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bill Davidsen <davidsen@tmr.com>
To: Burn Alting <burn@goldweb.com.au>
Cc: linux-raid@vger.kernel.org
Subject: Re: Hardware assisted parity computation - is it now worth it?
Date: Mon, 17 Jul 2006 14:05:21 -0400	[thread overview]
Message-ID: <44BBD161.5030609@tmr.com> (raw)
In-Reply-To: <1152778739.26511.65.camel@swtf.comptex.com.au>

Burn Alting wrote:

>Last year, there were discussions on this list about the possible
>use of a 'co-processor' (Intel's IOP333) to compute raid 5/6's
>parity data.
>
>We are about to see low cost, multi core cpu chips with very
>high speed memory bandwidth. In light of this, is there any
>effective benefit to such devices as the IOP333?
>  
>

Was there ever? Unless you're running on a really slow CPU, like 386, 
with a TB of RAID attached, and heavy CPU load, could anyone ever see a 
measureable performance gain? I haven't seen any such benchmarks, 
although I haven't looked beyond reading several related mailing lists.

>Or in other words, is a cheaper (power, heat, etc) cpu with
>higher memory access speeds, more cost effective than a
>bridge/bus device (ie hardware) solution (which typically
>has much lower memory access speeds)?
>
An additional device is always more complex, and less tunable than a CPU 
based solution. Except in the case above where there is very little CPU 
available, I don't see much hope for a cost (money and complexity) 
effective non-CPU solution.

Obviously my opinion only.

-- 
bill davidsen <davidsen@tmr.com>
  CTO TMR Associates, Inc
  Doing interesting things with small computers since 1979


      parent reply	other threads:[~2006-07-17 18:05 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-13  8:18 Hardware assisted parity computation - is it now worth it? Burn Alting
2006-07-13 10:13 ` Gordon Henderson
2006-07-13 21:16 ` Dan Williams
2006-07-13 23:43   ` Burn Alting
2006-07-17 18:05 ` Bill Davidsen [this message]

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=44BBD161.5030609@tmr.com \
    --to=davidsen@tmr.com \
    --cc=burn@goldweb.com.au \
    --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.