Multi-Architecture File System Build Using Layered Caching

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Users face inefficiencies in building file systems for multiple CPU architectures, leading to wasted time and storage due to the need for separate builds on each platform, duplication of platform-independent layers, and inability to utilize cached or shared layers across platforms.

Innovation Solution

A method that retrieves and caches platform-independent layers, allowing for cross-building and storage of a single image that supports multiple platforms, reducing the need for redundant builds and storage by marking platform-independent layers and using QEMU for cross-building platform-dependent layers.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If separate file system builds are performed for each CPU architecture platform, then platform-specific compatibility is ensured, but build time and storage space are significantly wasted due to duplication of platform-independent layers

Engineering Contradiction:

Improveplatform-specific compatibilityVSAvoidbuild time

Core Design Contradiction:

ReliabilityVSLoss of time

Solution Approach 1:

The patent segments the file system image into distinct layers: platform-independent layers and platform-dependent layers. This segmentation allows the build system to selectively cache and reuse platform-independent layers across multiple platforms while maintaining platform-specific compatibility through separate platform-dependent layers for each CPU architecture.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The patent creates a universal cache mechanism that stores platform-independent layers in a shared repository accessible by all platform build processes. This universal cache allows the same layer to be reused across x86, ARM, and other CPU architectures, eliminating redundant builds while maintaining platform-specific requirements through architecture-specific layer generation when needed.

Inventive Principle:

Principle #6Universality (Multi-functionality)

2Reliability

If separate file system builds are performed for each CPU architecture platform, then platform-specific compatibility is ensured, but storage space is significantly wasted due to duplication of platform-independent layers

Engineering Contradiction:

Improveplatform-specific compatibilityVSAvoidstorage space

Core Design Contradiction:

ReliabilityVSLoss of substance

Solution Approach 1:

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The patent implements a cache mechanism that creates and stores copies of platform-independent layers in a shared repository. These cached layers are then referenced and reused by multiple platform build processes, eliminating the need to store duplicate copies of the same layer across different platform-specific builds, thereby significantly reducing total storage requirements.

Inventive Principle:

Principle #26Copying

3Reliability

If platform-independent layers are rebuilt for each platform, then platform-specific optimization is achieved, but build efficiency is significantly reduced

Engineering Contradiction:

Improveplatform-specific optimizationVSAvoidbuild efficiency

Core Design Contradiction:

ReliabilityVSProductivity

Solution Approach 1:

The patent implements a cache mechanism that performs preliminary building of platform-independent layers and stores them in advance in a shared cache repository. When building for multiple platforms, the system first checks the cache for existing platform-independent layers, retrieving them without rebuilding, thereby significantly improving build efficiency while maintaining the ability to perform platform-specific optimization when necessary.

Inventive Principle:

Principle #10Preliminary action

Data Source

PatentUS11809376B2Building a file system for multiple architectures

Publication Date: 2023.11.07 INTERNATIONAL BUSINESS MACHINE CORPORATION

AI summary

In an approach to building a file system for multiple architectures, responsive to receiving a manifest for a file system build, a base layer is retrieved for each platform to be built, where the base layer is an operating system base. Responsive to determining that any layer to be built has not been built, the next layer to be built is retrieved. Responsive to the next layer to be built is platform-independent, the next layer is retrieved from a cache, where the next layer supports each platform. Responsive to the next layer to be built is platform-dependent, the next layer is built, where a copy of the next layer is built for each platform. The above steps are iteratively repeated until each layer is built. A single image of a completed file system build is stored, where the single image supports each platform.