From: Artem Bityutskiy <dedekind@infradead.org>
To: Ricard Wanderlof <ricard.wanderlof@axis.com>
Cc: linux-mtd <linux-mtd@lists.infradead.org>
Subject: Re: Eraseblocks torture: OneNAND results
Date: Fri, 08 Dec 2006 15:52:30 +0200 [thread overview]
Message-ID: <1165585950.3975.15.camel@sauron> (raw)
In-Reply-To: <Pine.LNX.4.64.0612081405270.22217@lnxricardw.se.axis.com>
Hello Ricard,
On Fri, 2006-12-08 at 14:43 +0100, Ricard Wanderlof wrote:
> Isn't 100000 a figure quoted by the flash manufacturer to be the _minimum_
> number of erase cycles, a specification which all devices must meet, even
> at extreme operating conditions (e.g. high temperature and extreme supply
> voltages)? That would imply that during more ordinary conditions, a random
> sample of flash chip would very likely be erasable many more times.
Probably. Not sure. Need to carefully look to the manual. Do not have it
now handy. But probably you are right. Also HW guys say that such a very
frequent erase may matter.
> Another thing: Why implement it as a kernel module? Speed I would assume?
Yeah, wanted to make it quicker.
--
Best regards,
Artem Bityutskiy (Битюцкий Артём)
next prev parent reply other threads:[~2006-12-08 13:53 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-08 2:00 Eraseblocks torture: OneNAND results Kyungmin Park
2006-12-08 6:19 ` Artem Bityutskiy
2006-12-08 13:43 ` Ricard Wanderlof
2006-12-08 13:52 ` Artem Bityutskiy [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-12-22 7:58 Kyungmin Park
2006-12-22 9:22 ` Artem Bityutskiy
2006-12-15 5:02 Kyungmin Park
2006-12-15 7:54 ` Enrico Migliore
2006-12-15 8:44 ` Ricard Wanderlof
2006-12-21 15:30 ` Jarkko Lavinen
2006-12-11 8:31 Kyungmin Park
2006-12-13 13:46 ` Artem Bityutskiy
2006-12-08 7:42 Kyungmin Park
2006-12-08 8:08 ` Artem Bityutskiy
2006-12-08 13:30 ` Artem Bityutskiy
2006-12-07 14:30 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=1165585950.3975.15.camel@sauron \
--to=dedekind@infradead.org \
--cc=linux-mtd@lists.infradead.org \
--cc=ricard.wanderlof@axis.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