Fabric Interface Transactional Synchronization Distributed Objects
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
As distributed computing systems grow in size and scale, memory access conflicts arise due to read/write requests across local and remote network devices, leading to inefficiencies in processor-intensive computations and data storage.
Innovation Solution
A system for transactional synchronization of distributed objects in a fabric architecture, where computing nodes communicate via a network switch, using transactional synchronization extensions to manage object associations and transactions across multiple address spaces, ensuring coherent memory access and conflict resolution.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Power
If distributed computing systems grow in size and scale to increase compute performance and storage capacity, then processing power and data storage capability are improved, but memory access conflicts increase due to read/write requests across local and remote network devices
Solution Approach 1:
The system segments memory access operations into discrete transactions with unique identifiers. Each transaction is broken down into readable and writable object references that can be independently tracked and managed, allowing the fabric interface to process and synchronize access requests without conflicts in distributed systems
Solution Approach 2:
The fabric interface acts as an intermediary between processor cores and distributed memory resources. It receives transaction requests, manages object associations, and coordinates access across local and remote devices, preventing memory access conflicts by centralizing control of distributed memory operations
2Quantity of substance
If distributed systems use multiple interconnected computing nodes to store information, then storage capacity is improved, but read/write access requests from local and remote processors lead to memory access conflicts
Solution Approach 1:
The system performs preliminary actions by establishing transaction associations with object references before actual read/write operations occur. The fabric interface pre-registers readable and writable objects with unique transaction identifiers, enabling efficient conflict-free access to distributed storage resources when data operations are subsequently executed
Solution Approach 2:
The fabric interface implements feedback mechanisms by tracking transaction states and object associations across distributed nodes. It monitors memory access requests and provides synchronization feedback to coordinating processors, ensuring that read/write operations maintain consistency and efficiency in large-scale distributed storage systems
Data Source
AI summary
Technologies for performing switch-based collective operations in a fabric architecture include a computing node that includes a host fabric interface (HFI) usable to communicate with network computing devices of the fabric architecture. The HFI is configured to associate an object with a transaction identifier generated by the HFI for a corresponding transactional synchronization session managed by the HFI of the computing node. Additionally, the HFI is configured to store received data associated with received write transaction that include the transaction identifier in a local buffer of the HFI. Upon receiving a transactional synchronization session termination request, the HFI is configured to initiate a write of the data stored in the local buffer of the HFI to one of the one or more data storage devices of the computing node. Other embodiments are described herein.