Bus Bandwidth Arbitration via Pending Read Counter

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current bus management systems face challenges in optimizing the ratio of read and write requests to efficiently utilize bandwidth between a host system and peripheral devices, leading to potential bottlenecks and resource under/over-utilization.

Innovation Solution

A method and system that utilize a pending read counter and threshold to dynamically manage the ratio of read and write requests by incrementing and decrementing the counter based on data received, comparing it against thresholds to select appropriate schemes for prioritizing requests, ensuring optimal bandwidth utilization.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If the peripheral device sends read requests to maximize data transfer, then bandwidth utilization improves, but the bus may become overloaded and bottlenecks occur

Engineering Contradiction:
Improvebandwidth utilizationVSAvoidbus overload
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The system implements feedback through the pending read counter that continuously monitors the state of read requests and adjusts the arbitration scheme accordingly. The counter reflects the current load on the bus and provides real-time feedback to the arbitrator, enabling dynamic adaptation of the request sending strategy to prevent overload while maximizing bandwidth utilization.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The arbitration scheme transitions from static to dynamic by changing the ratio of read to write requests based on the pending read counter value. The system dynamically adjusts its behavior by selecting different arbitration schemes (e.g., aggressive read-heavy, balanced, or conservative write-heavy) according to current bus conditions, allowing optimal performance across varying load scenarios.

Inventive Principle:
Principle #15Dynamics

2Reliability

If the peripheral device prioritizes write requests to ensure data integrity, then reliability improves, but bandwidth utilization decreases due to reduced read operations

Engineering Contradiction:
Improvedata integrityVSAvoidbandwidth utilization
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The system dynamically adjusts the read-write request ratio based on bus conditions rather than maintaining a fixed priority scheme. When the pending read counter indicates low load, the system can prioritize reads to maximize bandwidth; when load is high, it shifts toward more write requests to ensure data integrity, thus adaptively balancing reliability and productivity.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The arbitration scheme changes key parameters (the ratio of read to write requests) based on the state of the pending read counter. By modifying these parameters dynamically, the system can shift between aggressive data transfer modes and conservative data integrity modes, optimizing the trade-off between bandwidth utilization and reliability according to current conditions.

Inventive Principle:
Principle #35Parameter changes

3Device complexity

If the peripheral device uses a fixed ratio of read and write requests, then device complexity is reduced, but bandwidth optimization is limited

Engineering Contradiction:
Improvearbitration logicVSAvoidbandwidth efficiency
Core Design Contradiction:
Device complexityVSProductivity

Solution Approach 1:

The system implements self-service through the pending read counter, which automatically tracks the state of read requests without external intervention. This self-monitoring mechanism enables the arbitrator to make informed decisions about request prioritization, achieving bandwidth optimization through automated, context-aware arbitration rather than complex external control logic.

Inventive Principle:
Principle #25Self-service

4Productivity

If the peripheral device dynamically adjusts request ratios based on bus conditions, then bandwidth efficiency improves, but device complexity increases due to additional control logic

Engineering Contradiction:
Improvebandwidth efficiencyVSAvoidcontrol logic
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The pending read counter serves as a feedback mechanism that provides the arbitrator with real-time information about bus load conditions. This feedback enables the system to automatically adjust its request sending strategy without requiring complex external control logic, achieving bandwidth efficiency through a relatively simple feedback-driven arbitration mechanism.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS8850085B2Bandwidth aware request throttling
Publication Date: 2014.09.30 ORACLE INT CORP
  • US8850085B2 patent drawing
  • US8850085B2 patent drawing
  • US8850085B2 patent drawing

AI summary

A method for managing bandwidth of a bus connecting a peripheral device to a host system includes sending, over the bus, a first read request to the host system, incrementing a pending read counter by an amount corresponding to the requested data, receiving, in response to sending the first read request, at least a portion of the requested data from the host system, decrementing the pending read counter by an amount corresponding to the at least the portion of the requested data, and comparing the counter and a threshold to obtain a result. Based on the result, a scheme is selected for managing the bandwidth of the bus. The scheme specifies a ratio of read requests and write requests to be sent on the bus. The method further includes sending, based on the scheme, a second request that is a write request or a second read request.