From: Tanya Brokhman <tlinder@codeaurora.org>
To: Richard Weinberger <richard.weinberger@gmail.com>
Cc: Artem Bityutskiy <dedekind1@gmail.com>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [RFC/PATCH] mtd: ubi: Free peb's synchronously for fastmap
Date: Mon, 07 Apr 2014 19:05:47 +0300 [thread overview]
Message-ID: <5342CCDB.3080402@codeaurora.org> (raw)
In-Reply-To: <CAFLxGvyUsLZsi3iiape6BivaduvfqZh8kXXwYOFuExUJho09kg@mail.gmail.com>
On 4/7/2014 4:02 PM, Richard Weinberger wrote:
> On Tue, Apr 1, 2014 at 10:01 AM, Tanya Brokhman <tlinder@codeaurora.org> wrote:
>> At first mount it's possible that there are not enough free PEBs since
>> there are PEB's pending to be erased. In such scenario, fm_pool (which is
>> the pool from which user required PEBs are allocated) will be empty.
>> Try fixing the above described situation by synchronously performing
>> pending erase work, thus produce another free PEB.
>>
>> Signed-off-by: Tatyana Brokhman <tlinder@codeaurora.org>
>>
>> diff --git a/drivers/mtd/ubi/wl.c b/drivers/mtd/ubi/wl.c
>> index 457ead3..9a36f78 100644
>> --- a/drivers/mtd/ubi/wl.c
>> +++ b/drivers/mtd/ubi/wl.c
>> @@ -595,10 +595,29 @@ static void refill_wl_pool(struct ubi_device *ubi)
>> static void refill_wl_user_pool(struct ubi_device *ubi)
>> {
>> struct ubi_fm_pool *pool = &ubi->fm_pool;
>> + int err;
>>
>> return_unused_pool_pebs(ubi, pool);
>>
>> for (pool->size = 0; pool->size < pool->max_size; pool->size++) {
>> +retry:
>> + if (!ubi->free.rb_node ||
>> + (ubi->free_count - ubi->beb_rsvd_pebs < 1)) {
>> + /*
>> + * There are no available PEBs. Try to free
>> + * PEB by means of synchronous execution of
>> + * pending works.
>> + */
>> + if (ubi->works_count == 0)
>> + break;
>> + spin_unlock(&ubi->wl_lock);
>> + err = do_work(ubi);
>> + spin_lock(&ubi->wl_lock);
>
> This is basically what produce_free_peb() does.
Right. I didn't use t just because of the termination condition.
produce_free_peb stops if there is 1 free peb. I need more then 1
>
>> + if (err < 0)
>> + break;
>> + goto retry;
>> + }
>> +
>> pool->pebs[pool->size] = __wl_get_peb(ubi);
>
> __wl_get_peb() already calls produce_free_peb() when we run out of free PEBs.
>
> Does your patch really fix a problem you encounter or did you find the
> issue by reviewing
> the code?
>
Yes. We encountered this issue, as described in the commit message. This
is the fix. Verified and working for us.
--
QUALCOMM ISRAEL, on behalf of Qualcomm Innovation Center, Inc. is a member
of Code Aurora Forum, hosted by The Linux Foundation
next prev parent reply other threads:[~2014-04-07 16:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-01 8:01 [RFC/PATCH] mtd: ubi: Free peb's synchronously for fastmap Tanya Brokhman
2014-04-07 5:21 ` Dolev Raviv
2014-04-07 13:02 ` Richard Weinberger
2014-04-07 16:05 ` Tanya Brokhman [this message]
2014-04-07 16:42 ` Richard Weinberger
2014-04-08 13:42 ` Artem Bityutskiy
2014-04-08 13:44 ` Bityutskiy, Artem
2014-04-08 22:17 ` Richard Weinberger
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=5342CCDB.3080402@codeaurora.org \
--to=tlinder@codeaurora.org \
--cc=dedekind1@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=richard.weinberger@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;
as well as URLs for NNTP newsgroup(s).