From: Artem Bityutskiy <dedekind1@gmail.com>
To: hejianet <hejianet@linux.vnet.ibm.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: jffs2 copy too long after mounting
Date: Mon, 12 Nov 2012 17:42:46 +0200 [thread overview]
Message-ID: <1352734966.2262.13.camel@sauron.fi.intel.com> (raw)
In-Reply-To: <5089EB4B.5020800@linux.vnet.ibm.com>
[-- Attachment #1: Type: text/plain, Size: 665 bytes --]
On Fri, 2012-10-26 at 09:45 +0800, hejianet wrote:
> Sorry,maybe my question is long and bothering:(
> I try to make it more easily and clearly
> in jffs2_garbage_collect_deletion_dirent(),
> what does it mean, why in nand, we can't actually mark nodes obsolete
> pernamently
> /* On a medium where we can't actually mark nodes obsolete
> pernamently, such as NAND flash, ..... */
Because in NAND you cannot change the contents of a NAND page which has
already been written, because you have ECC for the data in the OOB. So
you cannot just mark a node as obsolete "in-place". In NOR you can do
this.
--
Best Regards,
Artem Bityutskiy
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2012-11-12 15:42 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <50881109.3010107@linux.vnet.ibm.com>
2012-10-25 1:41 ` jffs2 copy too long after mounting hejianet
2012-10-26 1:45 ` hejianet
2012-11-12 15:42 ` Artem Bityutskiy [this message]
2012-08-02 3:04 hejianet
2012-08-02 3:16 ` hejianet
2012-08-06 22:54 ` Brian Norris
2012-08-02 5:58 ` hejianet
2012-08-06 23:02 ` Brian Norris
2012-08-09 5:31 ` hejianet
2012-08-24 7:53 ` Artem Bityutskiy
2012-10-23 7:13 ` hejianet
2012-11-12 15:35 ` 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=1352734966.2262.13.camel@sauron.fi.intel.com \
--to=dedekind1@gmail.com \
--cc=hejianet@linux.vnet.ibm.com \
--cc=linux-mtd@lists.infradead.org \
/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.