mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Richard Weinberger <richard@nod.at>
To: Shmulik Ladkani <shmulik.ladkani@gmail.com>
Cc: linux-mtd@lists.infradead.org, dedekind1@gmail.com,
	linux-kernel@vger.kernel.org, Heinz.Egger@linutronix.de,
	tim.bird@am.sony.com, tglx@linutronix.de
Subject: Re: [PATCH] [RFC] UBI: Implement Fastmap support
Date: Wed, 23 May 2012 09:43:03 +0200	[thread overview]
Message-ID: <4FBC9507.9070200@nod.at> (raw)
In-Reply-To: <20120523091856.4e9217a2@pixies.home.jungo.com>

On 23.05.2012 08:18, Shmulik Ladkani wrote:
>> It removes a PEB from the free rb-tree.
>> ubi->lookuptbl[pnum] does not matter at this time.
>
> For practical matters, you are correct.
> Design wise, it is bit inconsistent and confusing.
>
> On one hand, you claim above that 'ubi->lookuptbl' holds the WL entries
> known to WL subsystem - that is, lookuptbl is a data structure used and
> maintained by the WL subsystem.
> OTOH, when a PEB is removed from hands of WL (by a ubi_wl_get_fm_peb
> call), you keep its WL entry assigned in ubi->lookuptbl.
>
> I'll rethink this, see if there's a potential trouble here.

If I remove the PEB from ubi->lookuptbl I'll have to reread the EC 
header upon ubi_wl_put_fm_peb().
Otherwise it's EC value is lost.

>>> However 'ubi_wl_put_fm_peb' creates a 'ubi_wl_entry' if not found in
>>> the lookuptbl.
>> Currently fastmap "fixes" ubi->lookuptbl on demand. Is this a problem?
>
> I guess not.
>
> The only problem, as previously noted, is the failure to create a new
> 'ubi_wl_entry' when the PEB needs to be returned to WL subsystem.

I think I can return them to the lookuptbl while attaching.

Stay tuned, I'll release v7 today or tomorrow.

Thanks,
//richard

  reply	other threads:[~2012-05-23  7:43 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-21 14:01 [RFC v6] UBI: Fastmap support (aka checkpointing) Richard Weinberger
2012-05-21 14:01 ` [PATCH] [RFC] UBI: Implement Fastmap support Richard Weinberger
2012-05-22 13:43   ` Artem Bityutskiy
2012-05-22 15:01   ` Shmulik Ladkani
2012-05-22 16:55     ` Richard Weinberger
2012-05-22 18:18       ` Shmulik Ladkani
2012-05-22 18:57         ` Richard Weinberger
2012-05-23  6:18           ` Shmulik Ladkani
2012-05-23  7:43             ` Richard Weinberger [this message]
2012-05-22 20:11         ` Richard Weinberger
2012-05-24  8:19           ` Artem Bityutskiy
2012-05-24  8:26             ` Richard Weinberger
2012-05-24  9:21               ` Artem Bityutskiy
2012-05-24  8:17       ` Artem Bityutskiy
2012-05-24  9:56         ` Shmulik Ladkani
2012-05-24 10:03           ` Richard Weinberger
2012-05-24 20:07             ` Shmulik Ladkani
2012-05-24  8:22       ` Artem Bityutskiy
2012-05-24  8:24         ` Richard Weinberger
2012-05-23 11:06 [RFC v7] UBI: Fastmap support (aka checkpointing) Richard Weinberger
2012-05-23 11:06 ` [PATCH] [RFC] UBI: Implement Fastmap support Richard Weinberger
2012-05-26 13:22   ` Artem Bityutskiy
2012-05-31 10:37   ` Adrian Hunter
2012-05-31 13:31     ` Richard Weinberger
2012-06-01  5:47   ` Adrian Hunter
2012-06-01  8:00     ` Richard Weinberger
2012-06-01  8:10       ` Artem Bityutskiy
2012-06-01  8:10         ` Richard Weinberger
2012-06-01  8:47           ` Adrian Hunter

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=4FBC9507.9070200@nod.at \
    --to=richard@nod.at \
    --cc=Heinz.Egger@linutronix.de \
    --cc=dedekind1@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=shmulik.ladkani@gmail.com \
    --cc=tglx@linutronix.de \
    --cc=tim.bird@am.sony.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

Powered by JetHome