From: xiaochuan-xu <xiaochuan-xu@cqu.edu.cn>
To: dedekind@infradead.org
Cc: linux-mtd <linux-mtd@lists.infradead.org>
Subject: Re: [PATCH][UBI]:Remove the prot tree from the WL unit
Date: Wed, 16 Jul 2008 22:36:11 +0800 [thread overview]
Message-ID: <416218737.17674@cqu.edu.cn> (raw)
Message-ID: <1216218971.2782.112.camel@localhost.localdomain> (raw)
In-Reply-To: <1216218036.29469.64.camel@sauron>
On Wed, 2008-07-16 at 17:20 +0300, Artem Bityutskiy wrote:
> On Wed, 2008-07-16 at 22:20 +0800, xiaochuan-xu wrote:
> > Hi,
> >
> > > Cool, thanks. However, if I grep for "prot", I still find
> > > some traces of protection trees. Try this. They should be
> > > removed as well.
> > >
> >
> > Yes, a few "protect" words are still in the wl.c file.
> > but I the are not relative to the PROT tree.
>
> Ok, sorry, I'll look closer again.
>
one problem,without the prot tree, is that when
ubi_io_read_vid_hdr(ubi, e1->pnum, vid_hdr, 0) (in the
wear_leveling_worker function())return errorcode equals to
UBI_IO_PEB_FREE, such PEB @e1 has to insert back to @used/scrub tree.
a bit later, one other wear-leveling worker will select the some PEB
(@e1 above), UBI_IO_PEB_FREE returns again.
over and over agin.
--
yours Sincerely,
xiaochuan-xu (许小川)
next parent reply other threads:[~2008-07-16 14:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1216214483.2782.91.camel@localhost.localdomain>
[not found] ` <1216217566.29469.62.camel@sauron>
[not found] ` <1216218027.2782.97.camel@localhost.localdomain>
[not found] ` <1216218036.29469.64.camel@sauron>
[not found] ` <1216218971.2782.112.camel@localhost.localdomain>
2008-07-16 14:36 ` xiaochuan-xu [this message]
[not found] ` <1216219840.29469.81.camel@sauron>
[not found] ` <1216264662.2781.15.camel@localhost.localdomain>
2008-07-17 3:17 ` [PATCH][UBI]:Remove the prot tree from the WL unit xiaochuan-xu
2008-07-17 9:40 ` Artem Bityutskiy
[not found] <1216205347.2782.63.camel@localhost.localdomain>
2008-07-16 10:49 ` xiaochuan-xu
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=416218737.17674@cqu.edu.cn \
--to=xiaochuan-xu@cqu.edu.cn \
--cc=dedekind@infradead.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox