Boot Partition Mount Time Reduction via Master Table Caching
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current data storage device mount processes are too slow for applications like automotive backup cameras, where early access to the boot partition is critical, due to the time-consuming nature of the existing mount process which treats all partitions equally, resulting in poor read latency for the boot partition.
Innovation Solution
The solution involves caching boot partition pointers in the master table instead of the translation table, allowing the data storage device to send a 'ready' signal earlier and provide faster access to the boot partition by suspending the mount process for a specific window to receive the boot partition read command, thereby reducing the mount time of the boot partition.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Loss of time
If the storage device mounts the entire storage device system using a traditional mount process, then all partitions can be accessed, but the mount time is too long for applications requiring early access to the boot partition
Solution Approach 1:
The mount process is segmented into two phases: a fast boot read path that mounts only the boot partition and a full mount path that mounts all partitions. This segmentation allows the system to provide early read access to the boot partition without completing the entire mount process, resolving the contradiction between reducing mount time and maintaining read access capability.
Solution Approach 2:
The boot partition is mounted in advance during the fast boot read path before other partitions. By performing preliminary mounting of the boot partition, the system enables early read access to boot-related data without waiting for the complete mount process to finish all partitions.
2Ease of operation
If the storage device treats all partitions equally in the mount process, then the mount process is simple to manage, but the boot partition read latency is poor
Solution Approach 1:
Different quality of service is provided to different partitions: the boot partition receives prioritized fast mounting and read access, while other partitions follow the standard mount process. This local quality differentiation improves boot partition read latency without complicating the overall mount process management.
Solution Approach 2:
The mount process becomes dynamic by supporting two different execution paths: a fast boot read path for boot partition access and a full mount path for complete system mounting. The system can switch between these paths based on the requested operation, providing dynamic optimization for boot partition access while maintaining simple management through a unified interface.
Data Source
AI summary
The disclosure relates to optimizing a mount process at a data storage device. The storage device communicates with a host using a mount process and mounts a master table, the master table caching translation table pointers associated with a boot partition. The storage device then sends a ready signal to the host indicating that the storage device is ready to receive a boot partition read command from the host. The storage device suspends the mount process for a window of time to receive the boot partition read command and executes the boot partition read command if the boot partition read command is received during the window of time. Accordingly, by caching boot partition pointers in the master table, the mount time of the boot partition is shortened to allow the storage device to send the ready signal earlier and provide the host with earlier access to the boot partition.


