From: Richard Weinberger <richard@nod.at>
To: Pintu Agarwal <pintu.ping@gmail.com>
Cc: linux-fsdevel <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: Tue, 26 Mar 2024 15:10:24 +0100 (CET) [thread overview]
Message-ID: <815707414.105612.1711462224601.JavaMail.zimbra@nod.at> (raw)
In-Reply-To: <CAOuPNLik9B0spBUYOVSekAns+zf=-zemit=DoVt0r6Us71p=Gw@mail.gmail.com>
Pintu,
----- Ursprüngliche Mail -----
> Von: "Pintu Agarwal" <pintu.ping@gmail.com>
> Is there anything missing here ?
> Can we increase the pool size ? Will it help to improve the timing ?
As long you see "scanning is finished", fastmap was not used.
Usually a fastmap is created after ubidetach or writing more than pool size.
>> 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.
>>
> Sorry, I could not get this fully.
> Is it possible to elaborate more with some reference ?
> Do we have some special commands/parameters to do it if we use initramfs ?
You need to touch code for that. These are highly specific adoptions.
Thanks,
//richard
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
prev parent reply other threads:[~2024-03-26 14:10 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
2024-03-26 13:45 ` Pintu Agarwal
2024-03-26 14:10 ` Richard Weinberger [this message]
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=815707414.105612.1711462224601.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 read-only IMAP folder(s) and NNTP newsgroup(s).