From: AKASHI Takahiro <takahiro.akashi@linaro.org>
To: Stefan Roese <sr@denx.de>
Cc: u-boot@lists.denx.de, Simon Glass <sjg@chromium.org>,
Heinrich Schuchardt <xypron.glpk@gmx.de>
Subject: Re: [RFC PATCH] disk: Don't loop over MAX_SEARCH_PARTITIONS in part_create_block_devices()
Date: Wed, 11 Jan 2023 10:32:41 +0900 [thread overview]
Message-ID: <20230111013241.GA42466@laputa> (raw)
In-Reply-To: <20230110080038.180628-1-sr@denx.de>
Hi,
Thank you for catching this issue.
On Tue, Jan 10, 2023 at 09:00:38AM +0100, Stefan Roese wrote:
> I've noticed that the first ext4 file loading from a MMC partition for
> ZynqMP takes quite some time (~ 1 second). Debugging showed, that the
> MMC driver reads the partition info 128 time (MAX_SEARCH_PARTITIONS)
> resulting in this boot delay. To fix this, let's just end creating the
> block drives in part_create_block_devices() when no more valid partition
> is found. This reduces the first file reading from ~0.9s to ~0.3s.
>
> Signed-off-by: Stefan Roese <sr@denx.de>
> Cc: Simon Glass <sjg@chromium.org>
> Cc: AKASHI Takahiro <takahiro.akashi@linaro.org>
> Cc: Heinrich Schuchardt <xypron.glpk@gmx.de>
> ---
> Reasoning for RFC:
> I did not dig into the current disk / partition stuff too deeply, so I'm
> not 100% sure that this patch does not break anything.
I'm afraid that this fix won't work for all the partition types,
especially for those in which entries in a partition table can be sparsely filled,
or in other words, valid partition numbers may not always be contiguous
even if they don't reach a maximum number.
I somehow confirmed this against a GPT partition by using gdisk.
-Takahiro Akashi
> ---
> disk/disk-uclass.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/disk/disk-uclass.c b/disk/disk-uclass.c
> index d32747e2242d..2999f7285b5a 100644
> --- a/disk/disk-uclass.c
> +++ b/disk/disk-uclass.c
> @@ -36,7 +36,7 @@ int part_create_block_devices(struct udevice *blk_dev)
> /* Add devices for each partition */
> for (count = 0, part = 1; part <= MAX_SEARCH_PARTITIONS; part++) {
> if (part_get_info(desc, part, &info))
> - continue;
> + break;
> snprintf(devname, sizeof(devname), "%s:%d", blk_dev->name,
> part);
>
> --
> 2.39.0
>
next prev parent reply other threads:[~2023-01-11 1:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-10 8:00 [RFC PATCH] disk: Don't loop over MAX_SEARCH_PARTITIONS in part_create_block_devices() Stefan Roese
2023-01-11 1:32 ` AKASHI Takahiro [this message]
2023-01-11 8:05 ` Stefan Roese
2023-01-11 9:04 ` AKASHI Takahiro
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=20230111013241.GA42466@laputa \
--to=takahiro.akashi@linaro.org \
--cc=sjg@chromium.org \
--cc=sr@denx.de \
--cc=u-boot@lists.denx.de \
--cc=xypron.glpk@gmx.de \
/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