linux-kernel - RE: [PATCH v2 2/2] mmc: core: adjust polling interval for CMD1

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Thu, 4 Nov 2021 07:27:11 +0000
From:   Avri Altman <Avri.Altman@....com>
To:     Huijin Park <huijin.park@...sung.com>,
        Ulf Hansson <ulf.hansson@...aro.org>
CC:     "linux-mmc@...r.kernel.org" <linux-mmc@...r.kernel.org>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        Huijin Park <bbanghj.park@...il.com>
Subject: RE: [PATCH v2 2/2] mmc: core: adjust polling interval for CMD1

 
> In mmc_send_op_cond(), loops are continuously performed at the same
> interval of 10 ms.  However the behaviour is not good for some eMMC which
> can be out from a busy state earlier than 10 ms if normal.
> 
> Rather than fixing about the interval time in mmc_send_op_cond(), let's
> instead convert into using the common __mmc_poll_for_busy().
> 
> The reason for adjusting the interval time is that it is important to reduce the
> eMMC initialization time, especially in devices that use eMMC as rootfs.
That's an impressive improvement.
Can you share some of the use-cases in which 10ms reduction in boot time is required?

Thanks,
Avri