Interconnect Region Ordering for Latency Reduction

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current systems face challenges in efficiently managing the order of operations across un-ordered interconnects, which restricts bandwidth and increases latency, and also face issues in enforcing order on transactions that do not require it, leading to unnecessary latency and resource tying up.

Innovation Solution

The system introduces the ability to express which requests need to stay in order, allowing the server to maintain order as instructed, enabling transactions to be sent simultaneously and reducing latency and bandwidth restrictions. This is achieved through mechanisms such as acquire and release flags, and by partitioning addressable regions into strongly, weakly, and unordered orderable regions.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If the interconnect enforces order on all transactions to ensure correctness, then reliability is improved, but bandwidth is reduced and latency increases

Engineering Contradiction:
Improvetransaction ordering correctnessVSAvoidbandwidth
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent applies different ordering characteristics to different addressable regions. Some regions are configured as strongly-ordered (enforcing strict transaction order), while others are weakly-ordered or unordered (allowing reordering for performance). This local differentiation allows the system to maintain reliability where needed while maximizing bandwidth where ordering constraints are not required, directly resolving the contradiction between correctness and productivity.

Inventive Principle:
Principle #3Local quality

2Reliability

If the interconnect enforces order on all transactions, then reliability is improved, but latency increases due to resource tying up

Engineering Contradiction:
Improvetransaction ordering correctnessVSAvoidlatency
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

By configuring specific addressable regions as strongly-ordered rather than universally enforcing ordering, the patent reduces unnecessary serialization of transactions in regions where ordering is not critical. This allows transactions to proceed with minimal delay in weakly-ordered and unordered regions, reducing overall latency while maintaining reliability in regions where it is required.

Inventive Principle:
Principle #3Local quality

3Productivity

If transactions are sent simultaneously without ordering enforcement, then bandwidth is improved and latency is reduced, but ordering correctness deteriorates

Engineering Contradiction:
ImprovebandwidthVSAvoidtransaction ordering correctness
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The patent enables simultaneous transaction processing in weakly-ordered and unordered regions to maximize bandwidth, while maintaining strict ordering in strongly-ordered regions to ensure correctness. This spatial differentiation of ordering policies allows the system to achieve high productivity without sacrificing reliability, as each region operates under the appropriate ordering constraint for its specific requirements.

Inventive Principle:
Principle #3Local quality

Data Source

PatentUS20250173281A1Orderability of operations
Publication Date: 2025.05.29 SIFIVE INC
  • US20250173281A1 patent drawing
  • US20250173281A1 patent drawing
  • US20250173281A1 patent drawing

AI summary

A method for managing orders of operations between one or more clients and one or more servers is disclosed. The method includes partitioning addressable regions of logical servers on or within an interconnect link into multiple regions including a first orderable region, and providing logical client an ability to push ordering responsibility within the first orderable region to a server. Over the first orderable region, two request messages for access to memory-mapped sources including two respective operations are transmitted, and the two request messages originate from a same logical client. The ordering responsibility can include a first rule for order of operations between the two request messages.