Interconnect Routing Circuitry for Relative Data Width Indication

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Integrated circuits face inefficiencies in managing data access requests due to variations in read response data widths between ingress and egress ports, leading to unnecessary resource allocation and potential bottlenecks in data handling.

Innovation Solution

The interconnect includes routing circuitry that obtains a relative data width indication to determine if read responses at the egress port have a narrower data width than those required by the ingress port, allowing for optimized resource allocation and improved performance by selectively allocating resources based on this indication.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If resources are allocated for handling read responses without considering data width variations, then resource availability is ensured, but resource allocation efficiency deteriorates

Engineering Contradiction:
Improveresource allocation efficiencyVSAvoidresource allocation
Core Design Contradiction:
ProductivityVSQuantity of substance

Solution Approach 1:

The routing circuitry obtains a relative data width indication before allocating resources for handling read responses. This preliminary action allows the system to determine in advance whether the egress port will receive narrower read responses than the ingress port, enabling proactive and efficient resource allocation decisions without unnecessary resource reservation

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The system applies different resource allocation strategies based on the specific data width requirements of each port pair. By using the relative data width indication, the routing circuitry can allocate resources locally and specifically according to the actual needs of each ingress-egress port combination, rather than applying a uniform allocation policy across all ports

Inventive Principle:
Principle #3Local quality

2Productivity

If buffering resources are allocated for all read responses, then data handling capacity is ensured, but power consumption increases

Engineering Contradiction:
Improvedata handling capacityVSAvoidpower consumption
Core Design Contradiction:
ProductivityVSUse of energy by moving object

Solution Approach 1:

Instead of allocating buffering resources for all possible read responses, the system uses the relative data width indication to apply buffering only when necessary. When the indication shows that the egress port will receive narrower read responses, buffering resources are allocated; otherwise, buffering is skipped, achieving partial action that matches actual needs and reduces unnecessary power consumption

Inventive Principle:
Principle #16Partial or excessive action

3Ease of operation

If uniform resource allocation is used for all ports, then system simplicity is maintained, but latency increases due to unnecessary buffering

Engineering Contradiction:
Improvesystem simplicityVSAvoidlatency
Core Design Contradiction:
Ease of operationVSLoss of time

Solution Approach 1:

The system changes the allocation parameter from a uniform fixed policy to a dynamic policy based on the relative data width indication. This parameter change allows the system to adapt resource allocation to actual data width requirements, eliminating unnecessary buffering operations and reducing latency while maintaining ease of operation through automated decision-making

Inventive Principle:
Principle #35Parameter changes

Data Source

PatentUS10437750B2Relative data width indication for read responses routed by an interconnect
Publication Date: 2019.10.08 ARM LTD
  • US10437750B2 patent drawing
  • US10437750B2 patent drawing
  • US10437750B2 patent drawing

AI summary

An interconnect for providing data access between nodes of an integrated circuit, comprises a predetermined type of ingress port comprising routing circuitry responsive to a read-triggering request received from a requesting node to select from a selected egress port via which signals are to be routed to a destination node to control the destination node to return at least one read response dependent on data read from a target storage location. In response to the read-triggering request, the routing circuitry obtains a relative data width indication specifying whether read responses received at the selected egress port have a narrower data width than read responses to be provided to the requesting node by the predetermined type of ingress port, and controls allocation of resource for handling the read-triggering request or the at least one read response depending on the relative data width indication.