Virtual File System for PLD Configuration Management
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Managing the configuration of large-scale reconfigurable computing arrangements, such as those using programmable logic devices (PLDs), is complex due to low-level and unfamiliar interfaces, which can lead to scheduling, reliability, and cost issues, especially in multi-device systems like supercomputers where numerous devices and communication channels complicate software and hardware configuration management.
Innovation Solution
A method is introduced that creates a virtual file system hierarchy registered with the operating system, allowing for standardized file system calls to manage configuration data, including creating directories, mapping configuration data to resources, and controlling access rights, thereby simplifying the management of PLD configurations and enabling abstraction across different device architectures.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Ease of operation
If low-level interfaces (SelectMap, boundary scan, ICAP) are used to access PLD configuration data, then direct access capability is improved, but interface complexity and unfamiliarity increase
Solution Approach 1:
The patent introduces a virtual file system as an intermediary layer between the PLD configuration interfaces and the software applications. This virtual file system translates high-level file system operations into low-level PLD interface calls, providing abstraction that simplifies the interface while maintaining direct access capability. The virtual file system acts as a mediator that hides the complexity of the underlying hardware interfaces.
Solution Approach 2:
The patent segments the configuration management functionality into separate components: the virtual file system layer for abstraction, the PLD interface layer for hardware communication, and the configuration data layer for storage. This segmentation allows each layer to be optimized independently and simplifies the overall system by separating concerns.
2Adaptability or versatility
If multiple low-level interfaces are provided for accessing configuration data, then access flexibility is improved, but system complexity increases
Solution Approach 1:
The virtual file system provides a universal interface that can access all types of PLD configuration data through a single consistent mechanism. Instead of requiring different software code for each low-level interface (SelectMap, boundary scan, ICAP), the virtual file system unifies access to all configuration data through standard file system operations, making the system more versatile while reducing complexity.
3Manufacturing precision
If detailed configuration management is implemented for multi-device systems, then configuration accuracy is improved, but management complexity increases
Solution Approach 1:
The patent uses virtual file system entries as copies or representations of actual PLD configuration resources. These virtual entries provide an abstract view of the configuration data that can be manipulated independently of the underlying hardware. The virtual file system creates a copy of the configuration management interface that simplifies operations while maintaining accuracy through proper mapping to physical resources.
Data Source
AI summary
A top-level directory of a virtual file system is created. A hierarchy of directories is created under the top-level directory including creating a first file that contains an architecture description of the multi-device circuit arrangement. The directories have names indicative of the plurality of devices and configurable resources of the plurality of devices of the architecture description specified in the first file. A first set of one or more files is created that contain state data or configuration data for configuring resources of the plurality of devices to perform functions specified by the configuration data. A mapping of the configuration data to the resources of the plurality of devices is determined, and configuration data is stored in the configurable resources according to the mapping.