Forum Discussion

MBiek's avatar
MBiek
Icon for New Contributor rankNew Contributor
2 years ago

Unclear interpretation of readyAllowance in Avalon Streaming Interfaces

Hello, I have a question about the interpretation of the readyAllowance property in back-pressured Avalon ST interfaces. It would be great if someone could help me out. The Avalon specification def...
Platform
Wincent_Altera's avatar
Wincent_Altera
Icon for Regular Contributor rankRegular Contributor
2 years ago

Hi Martin,


First under section 5.4 explains the basic property of AVST interface.

You may choose to transfer your data with 5.9.1. Data Transfers Using readyLatency and readyAllowance or 5.9.2. Data Transfers Using readyLatency

The reason why the <n> transfers do not have to be consecutive is to allow for flexibility in the implementation of the Avalon ST interface.

In a system where back pressure is used to control the flow of data, it may be beneficial for the sink to have the ability to accept a burst of data even after indicating that it is not ready to accept more data. This flexibility allows for better utilization of the data path and can improve overall system performance.

By allowing the <n> transfers to be non-consecutive, the Avalon ST interface provides a mechanism for the sink to manage its data reception in a way that best suits its internal processing requirements.


Hope that answer your question.


Regards,

Wei Chuan