public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Richard Weinberger <richard@nod.at>,
	Miquel Raynal <miquel.raynal@bootlin.com>,
	Vignesh Raghavendra <vigneshr@ti.com>,
	Zhihao Cheng <chengzhihao1@huawei.com>
Cc: Linux MTD <linux-mtd@lists.infradead.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Fwd: ubi: fastmap: Fix a series of wear leveling problems
Date: Wed, 16 Aug 2023 16:56:44 +0700	[thread overview]
Message-ID: <44f5a8f7-0bf4-c986-a0dc-dc12d0cb30ca@gmail.com> (raw)

Hi,

I notice a bug report with proposed fixes on Bugzilla [1]. Quoting from it
(only the first problem that is quoted):

> Problem 1: large erase counter for single fastmap data PEB
> 
> Config:
> x86_64 qemu
> flash: nandsim
> CONFIG_MTD_UBI_WL_THRESHOLD=128
> CONFIG_MTD_UBI_FASTMAP=y
> ubi->beb_rsvd_pebs=0
> 
> Running fsstress on ubifs for 3h(fastmap data PEB has large erase counter than others):
> =========================================================
> from              to     count      min      avg      max
> ---------------------------------------------------------
> 0        ..        9:        0        0        0        0
> 10       ..       99:      532       84       92       99
> 100      ..      999:    15787      100      147      229
> 1000     ..     9999:       64     4699     4765     4826
> 10000    ..    99999:        0        0        0        0
> 100000   ..      inf:        1   272935   272935   272935
> ---------------------------------------------------------
> Total               :    16384       84      180   272935
> PEB 8031(ec=272935) is always taken for fastmap data.
> 
> After fix, running fsstress on ubifs for 12h(no pool reservation), no individual peb has big erase counter:
> =========================================================
> from              to     count      min      avg      max
> ---------------------------------------------------------
> 0        ..        9:        0        0        0        0
> 10       ..       99:        0        0        0        0
> 100      ..      999:    16320      609      642      705
> 1000     ..     9999:        0        0        0        0
> 10000    ..    99999:       64    18176    18234    18303
> 100000   ..      inf:        0        0        0        0
> ---------------------------------------------------------
> Total               :    16384      609      710    18303

See Bugzilla for the full thread (with other problems mentioned) and
attached patch series that fixes them.

Zhihao: I asked you on BZ to send your patches to linux-mtd list,
but you didn't respond there. Would you like to send them for
review?

Thanks.

[1]: https://bugzilla.kernel.org/show_bug.cgi?id=217787

-- 
An old man doll... just what I always wanted! - Clara

             reply	other threads:[~2023-08-16  9:57 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-16  9:56 Bagas Sanjaya [this message]
2023-08-16 11:08 ` Fwd: ubi: fastmap: Fix a series of wear leveling problems Zhihao Cheng

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=44f5a8f7-0bf4-c986-a0dc-dc12d0cb30ca@gmail.com \
    --to=bagasdotme@gmail.com \
    --cc=chengzhihao1@huawei.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=miquel.raynal@bootlin.com \
    --cc=richard@nod.at \
    --cc=vigneshr@ti.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