From: Ezequiel Garcia <ezequiel.garcia@free-electrons.com>
To: Huang Shijie <shijie8@gmail.com>
Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>,
dedekind1@gmail.com, Huang Shijie <b32955@freescale.com>,
linux-mtd@lists.infradead.org, computersforpeace@gmail.com,
dwmw2@infradead.org
Subject: Re: [PATCH v3 00/10] About the SLC/MLC
Date: Sat, 19 Oct 2013 10:32:06 -0300 [thread overview]
Message-ID: <20131019133205.GD2470@localhost> (raw)
In-Reply-To: <20130827033020.GA2182@gmail.com>
Hi Huang,
On Mon, Aug 26, 2013 at 11:30:22PM -0400, Huang Shijie wrote:
> On Mon, Aug 26, 2013 at 02:41:53PM +0200, Thomas Petazzoni wrote:
> >
> > On Mon, 26 Aug 2013 17:36:38 +0800, Huang Shijie wrote:
> > > In current mtd code, the MTD_NANDFLASH is used to represent both the
> > > SLC nand MLC(including the TLC). But we already have the MTD_MLCNANDFLASH
> > > to stand for the MLC. What is worse is that the JFFS2 may run on the MLC
> > > nand with current code. For the reason of READ/WRITE disturbance, the JFFS2
> > > should runs on the SLC only,
> >
> > Pardon the probably very silly question, but would you mind giving more
> > details about why JFFS2 is not appropriate on MLC flashes? Is there
> > anything that UBI/UBIFS does that JFFS2 isn't doing to take into
> > account read/write disturbance?
> I try to explain it.
>
> For the UBIFS, it will writes the page(including the oob) only one time;
> but for jffs2, it may writes the page(including the oob) twice, one for the
> marker, one for the real data.
>
It seems I overlooked this when I first read it.
Do you mean that JFFS2 will write twice: one write to the spare region,
one write in the data region, with no erase between those two?
I've looked at the JFFS2 code, but it's not trivial to follow :)
--
Ezequiel García, Free Electrons
Embedded Linux, Kernel and Android Engineering
http://free-electrons.com
next prev parent reply other threads:[~2013-10-19 13:32 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-26 9:36 [PATCH v3 00/10] About the SLC/MLC Huang Shijie
2013-08-26 9:36 ` [PATCH v3 01/10] mtd: nand: rename the cellinfo to bits_per_cell Huang Shijie
2013-08-27 17:10 ` Vikram Narayanan
2013-08-28 2:23 ` Huang Shijie
2013-08-28 2:42 ` Brian Norris
2013-08-28 2:45 ` Huang Shijie
2013-08-28 2:48 ` Brian Norris
2013-08-28 2:53 ` Huang Shijie
2013-08-28 3:02 ` Brian Norris
2013-08-28 3:09 ` Huang Shijie
2013-08-26 9:36 ` [PATCH v3 02/10] mtd: set the cell information for ONFI nand Huang Shijie
2013-08-26 9:36 ` [PATCH v3 03/10] mtd: print out the cell information for nand chip Huang Shijie
2013-08-26 9:36 ` [PATCH v3 04/10] mtd: gpmi: rewrite the gpmi_ecc_write_oob() to support the jffs2 Huang Shijie
2013-08-26 9:36 ` [PATCH v3 05/10] mtd: add more comment for MTD_NANDFLASH/MTD_MLCNANDFLASH Huang Shijie
2013-08-26 9:36 ` [PATCH v3 06/10] mtd: fix the wrong mtd->type for nand chip Huang Shijie
2013-08-28 3:08 ` Brian Norris
2013-08-28 6:59 ` Huang Shijie
2013-08-28 7:28 ` Brian Norris
2013-08-28 7:50 ` Huang Shijie
2013-08-28 9:26 ` Huang Shijie
2013-08-29 1:24 ` Huang Shijie
2013-08-29 5:05 ` Brian Norris
2013-08-29 5:34 ` Huang Shijie
2013-08-29 5:50 ` Huang Shijie
2013-09-04 18:51 ` Brian Norris
[not found] ` <52280278.6020007@freescale.com>
2013-09-17 0:13 ` Brian Norris
2013-08-26 9:36 ` [PATCH v3 07/10] jffs2: do not support the MLC nand Huang Shijie
2013-08-26 9:36 ` [PATCH v3 08/10] mtd: add MTD_MLCNANDFLASH case for mtd_type_show() Huang Shijie
2013-08-26 9:36 ` [PATCH v3 09/10] mtd: add a helper to detect the nand type Huang Shijie
2013-09-17 0:27 ` Brian Norris
2013-08-26 9:36 ` [PATCH v3 10/10] mtd: mtd-abi: " Huang Shijie
2013-08-26 12:41 ` [PATCH v3 00/10] About the SLC/MLC Thomas Petazzoni
2013-08-27 3:30 ` Huang Shijie
2013-10-19 13:32 ` Ezequiel Garcia [this message]
2013-10-21 2:58 ` Huang Shijie
2013-10-22 5:11 ` Gupta, Pekon
2013-10-30 22:02 ` Brian Norris
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=20131019133205.GD2470@localhost \
--to=ezequiel.garcia@free-electrons.com \
--cc=b32955@freescale.com \
--cc=computersforpeace@gmail.com \
--cc=dedekind1@gmail.com \
--cc=dwmw2@infradead.org \
--cc=linux-mtd@lists.infradead.org \
--cc=shijie8@gmail.com \
--cc=thomas.petazzoni@free-electrons.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.