From: Artem Bityutskiy <dedekind1@gmail.com>
To: Quentin Schulz <quentin.schulz@bootlin.com>,
richard@nod.at, dwmw2@infradead.org, computersforpeace@gmail.com,
boris.brezillon@bootlin.com, marek.vasut@gmail.com
Cc: linux-mtd@lists.infradead.org, linux-kernel@vger.kernel.org,
thomas.petazzoni@bootlin.com
Subject: Re: [PATCH v5 0/2] ubi: add possibility to skip CRC check for static UBI volumes
Date: Mon, 02 Jul 2018 16:49:56 +0300 [thread overview]
Message-ID: <1530539396.469.98.camel@gmail.com> (raw)
In-Reply-To: <cover.ab725a3c64626915f8184e28937870f36684db61.1530524405.git-series.quentin.schulz@bootlin.com>
On Mon, 2018-07-02 at 11:43 +0200, Quentin Schulz wrote:
> Some users of static UBI volumes implement their own integrity check, thus
> making the volume CRC check done at open time useless. For instance, this
> is the case when one use the ubiblock + dm-verity + squashfs combination,
> where dm-verity already checks integrity of the block device but this time
> at the block granularity instead of verifying the whole volume.
>
> Skipping this test drastically improves the boot-time.
>
> mtd-utils patches are already merged. See:
> http://git.infradead.org/mtd-utils.git/commit/9095d213f536aec0f3c37f6666177f3b907afde7
> http://git.infradead.org/mtd-utils.git/commit/7b4a65a27d2621b58c634d02c6a068ed9562383c
> http://git.infradead.org/mtd-utils.git/commit/5e9bc0daa41d84ce5de81c4a1665d65f51893c10
> http://git.infradead.org/mtd-utils.git/commit/8ba21ab75b41a1f9a6e27eed3ea80c9829669c5a
For the whole patch-set,
Reviewed-by: Artem Bityutskiy <artem.bityutskiy@linux.intel.com>
prev parent reply other threads:[~2018-07-02 13:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-02 9:43 [PATCH v5 0/2] ubi: add possibility to skip CRC check for static UBI volumes Quentin Schulz
2018-07-02 9:43 ` [PATCH v5 1/2] ubi: provide a way to skip CRC checks Quentin Schulz
2018-07-02 9:43 ` [PATCH v5 2/2] ubi: expose the volume CRC check skip flag Quentin Schulz
2018-07-02 13:49 ` Artem Bityutskiy [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=1530539396.469.98.camel@gmail.com \
--to=dedekind1@gmail.com \
--cc=boris.brezillon@bootlin.com \
--cc=computersforpeace@gmail.com \
--cc=dwmw2@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=marek.vasut@gmail.com \
--cc=quentin.schulz@bootlin.com \
--cc=richard@nod.at \
--cc=thomas.petazzoni@bootlin.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).