All of lore.kernel.org
 help / color / mirror / Atom feed
From: Artem Bityutskiy <dedekind1@gmail.com>
To: Atlant Schmidt <aschmidt@dekaresearch.com>
Cc: 'Matej Kupljen' <matej.kupljen@gmail.com>,
	Brian Norris <computersforpeace@gmail.com>,
	linux-mtd <linux-mtd@lists.infradead.org>
Subject: RE: Unstable bits and JFFS2
Date: Fri, 13 Apr 2012 19:27:42 +0300	[thread overview]
Message-ID: <1334334462.13160.10.camel@sauron.fi.intel.com> (raw)
In-Reply-To: <0A40042D85E7C84DB443060EC44B3FD3351F9CAD87@dekaexchange07.deka.local>

[-- Attachment #1: Type: text/plain, Size: 1483 bytes --]

On Wed, 2012-04-04 at 06:54 -0400, Atlant Schmidt wrote:
> Matej:
> 
> > Artem, you said that this unstable bits only happen
> > during power cuts, is this right? Would those appear
> > also on simulated power cuts, the ones that integck
> > can produce?
> 
>   (Note: This isn't Artem replying.)
> 
>   Unstable bits can happen anytime, but *REAL* power-cuts
>   while writing are certainly a great way to produce them;
>   after all, if you've only transferred half the electrons
>   to the floating gate when power goes away, well, that
>   Flash cell is now a roll-of-the-quantum-dice each time
>   you read it.
> 
>   Simulated power cuts (that just stop the software
>   processing at arbitrary and random points) can't
>   produce this effect.
> 
>   But any time a read-disturb or write-disturb takes place,
>   there's some probability that a Flash cell will be left
>   with a "near-threshold" charge on the floating gate, so
>   unstable bits are a fact of life that must be faced by
>   any software that drives NAND Flash memory chips. This
>   is, of course, especially true of MLC chips and even
>   more-true for TLC chips (with three bits per cell).

Yeah, thanks for correcting. Yeah, read/write-disturb may make bits to
become unstable, but we assume this is a slow process which will
gradually make more and more bits flip and ECC will take care of that.
So I think Matej can exclude this.

-- 
Best Regards,
Artem Bityutskiy

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

  parent reply	other threads:[~2012-04-13 16:24 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-28 11:16 Unstable bits and JFFS2 Matej Kupljen
2012-04-02 17:12 ` Brian Norris
2012-04-04  9:17   ` Matej Kupljen
2012-04-04 10:54     ` Atlant Schmidt
2012-04-10  7:22       ` Matej Kupljen
2012-04-13 16:27       ` Artem Bityutskiy [this message]
2012-04-13 16:40         ` Atlant Schmidt
2012-04-13 17:01           ` Artem Bityutskiy
2012-04-14  4:21             ` Ricard Wanderlof
2012-04-22 14:25               ` Artem Bityutskiy
2012-04-13 18:36         ` Wolfram Sang
2012-04-13 19:49           ` Artem Bityutskiy

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=1334334462.13160.10.camel@sauron.fi.intel.com \
    --to=dedekind1@gmail.com \
    --cc=aschmidt@dekaresearch.com \
    --cc=computersforpeace@gmail.com \
    --cc=linux-mtd@lists.infradead.org \
    --cc=matej.kupljen@gmail.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 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.