Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Why buffering a dataflow design matters? #4

Open
Mahdi89 opened this issue Jan 15, 2016 · 0 comments
Open

Why buffering a dataflow design matters? #4

Mahdi89 opened this issue Jan 15, 2016 · 0 comments

Comments

@Mahdi89
Copy link
Member

Mahdi89 commented Jan 15, 2016

To ensure deadlock-freedom a dataflow design needs to be buffered. In a simple language, it means data has to have available registers to move into, otherwise it would get stuck and cause the predecessor data tokens to pause/stall as well. This may raise a deadlock when the data tokens are stuck within a finite loop! which would never let the tokens to move; we technically call this situation a "deadlock" and needs the circuit to restart which may cause data loss!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant