public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: "Thomas Gleixner" <tglx@linutronix.de>
To: "Dan Brown" <brown@osdsun1.nrl.navy.mil>,
	"Slim" <slimaffi@yahoo.com>, <linux-mtd@lists.infradead.org>
Subject: Re: [PATCH] Towards DiskOnChip support as a NAND driver
Date: Wed, 16 Jun 2004 23:47:20 +0200	[thread overview]
Message-ID: <200406162347.20436.tglx@linutronix.de> (raw)
In-Reply-To: <083701c453df$c65db960$0100a8c0@superfortress>

On Wednesday 16 June 2004 22:23, Dan Brown wrote:
> > ECC - hardware error correction by the device?  Is this an optional
> > enable in the driver?
>
> Yes, the DOC has an ASIC that does ECC computation (for actual error
> correction, software assitance is required).  It's not optional, though it
> could be made so....  Why would you want to turn it off?

It has two advantages over software ECC.

1. The software ECC is a Hamming code which can correct 1 bit errors and 
detect 2 bit errors. The HW ECC on DOC devices is a Reed Solomon Encoder / 
Decoder which allows to correct and detect more errors

2. In general a HW based ECC generator is a lot faster than the software 
version as it gets you rid of a ugly loop through all the data bytes on each 
read / write.

A small drawback is the error correction for reed solomon, as it is more  
complex and slower than for hamming codes. This is not too bad as error 
correction usually starts to happen when the device wears out, but then the 
hamming code which we use in soft ecc can be rather unsufficient. 
The speed improvement on write and read is really worth to use hw ecc if its 
thers

-- 
Thomas
_____________________________________________________________________
From slash dot org
"When customers are visiting, engineers are not allowed to wear ties. 
That way the customer can tell who is the engineer and who is the 
salesman (and therefore whom to believe.). Ties cut off blood flow 
to the brain, making it easier for the salesmen to do their jobs." 
_____________________________________________________________________
linutronix - competence in embedded & realtime linux
http://www.linutronix.de
mail: tglx@linutronix.de

  reply	other threads:[~2004-06-16 21:53 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E1BacpZ-0008CJ-KT@canuck.infradead.org>
2004-06-16 16:13 ` [PATCH] Towards DiskOnChip support as a NAND driver Slim
2004-06-16 20:23   ` Dan Brown
2004-06-16 21:47     ` Thomas Gleixner [this message]
2004-06-16 14:19 Dan Brown
2004-06-16 22:32 ` Thomas Gleixner
2004-06-16 22:46   ` David Woodhouse
2004-06-16 22:50     ` Thomas Gleixner

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=200406162347.20436.tglx@linutronix.de \
    --to=tglx@linutronix.de \
    --cc=brown@osdsun1.nrl.navy.mil \
    --cc=linux-mtd@lists.infradead.org \
    --cc=slimaffi@yahoo.com \
    /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