From: Artem Bityutskiy <dedekind1@gmail.com>
To: Nishanth Menon <menon.nishanth@gmail.com>
Cc: Vimal Singh <vimal.newwork@gmail.com>,
Linux MTD <linux-mtd@lists.infradead.org>
Subject: Re: Question on partition wise ECC support
Date: Mon, 11 Jan 2010 08:09:04 +0200 [thread overview]
Message-ID: <1263190144.30988.25.camel@localhost.localdomain> (raw)
In-Reply-To: <782515bb1001060642v78e1c482we6612d8cb8ac041c@mail.gmail.com>
On Wed, 2010-01-06 at 08:42 -0600, Nishanth Menon wrote:
> Hi,
> Just a generic question: for NAND devices, each ECC strategy such as
> 256byte/512byte ecc has tradeoff b/w reliability Vs performance. I
> wonder if we have some mechanism if we can maintain different ECC
> strategy per partition.
I do not think it is possible.
--
Best Regards,
Artem Bityutskiy (Артём Битюцкий)
prev parent reply other threads:[~2010-01-11 6:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-06 14:42 Question on partition wise ECC support Nishanth Menon
2010-01-11 6:09 ` Artem Bityutskiy [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=1263190144.30988.25.camel@localhost.localdomain \
--to=dedekind1@gmail.com \
--cc=linux-mtd@lists.infradead.org \
--cc=menon.nishanth@gmail.com \
--cc=vimal.newwork@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox