From: Richard Weinberger <richard@nod.at>
To: Pintu Agarwal <pintu.ping@gmail.com>
Cc: linux-fsdevel@kvack.org,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
linux-mtd <linux-mtd@lists.infradead.org>,
Artem Bityutskiy <artem.bityutskiy@linux.intel.com>,
Richard Weinberger <richard.weinberger@gmail.com>,
Ezequiel Garcia <ezequiel@collabora.com>,
Miquel Raynal <miquel.raynal@bootlin.com>,
Vignesh Raghavendra <vigneshr@ti.com>
Subject: Re: linux-mtd: ubiattach taking long time
Date: Mon, 25 Mar 2024 19:20:02 +0100 (CET) [thread overview]
Message-ID: <321330094.101965.1711390802883.JavaMail.zimbra@nod.at> (raw)
In-Reply-To: <CAOuPNLjQPo8hoawK73H7FOVitQHp21HHODExO+7cguGrtURKWg@mail.gmail.com>
Pintu,
----- Ursprüngliche Mail -----
> Von: "Pintu Agarwal" <pintu.ping@gmail.com>
> I have tried using fastmap as well, but still no difference.
> Are there any other techniques to improve the ubiattach timing ?
>
> Logs:
> ----------
> Doing from initramfs:
> {{{
> [ 6.949143][ T214] ubi0: attaching mtd54
> [ 8.023766][ T214] ubi0: scanning is finished
No fastmap attach here.
Make sure to set fm_autoconvert:
http://www.linux-mtd.infradead.org/doc/ubi.html#L_fastmap
If set, UBI create after a few writes a fastmap.
Speaking of other techniques, you can improve scanning time also by
tuning UBI for your NAND controller/setup.
E.g. transferring only the amount of bytes needed for an header.
Or reading without ECC and re-reading with ECC if the header CRC-check fails.
Thanks,
//richard
next prev parent reply other threads:[~2024-03-25 18:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-25 16:57 linux-mtd: ubiattach taking long time Pintu Agarwal
2024-03-25 18:20 ` Richard Weinberger [this message]
2024-03-26 13:45 ` Pintu Agarwal
2024-03-26 14:10 ` 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=321330094.101965.1711390802883.JavaMail.zimbra@nod.at \
--to=richard@nod.at \
--cc=artem.bityutskiy@linux.intel.com \
--cc=ezequiel@collabora.com \
--cc=linux-fsdevel@kvack.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=miquel.raynal@bootlin.com \
--cc=pintu.ping@gmail.com \
--cc=richard.weinberger@gmail.com \
--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;
as well as URLs for NNTP newsgroup(s).