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

How experiments NoC fault-tolerant routing algorithm in the Noxim? #86

Open
Seeker-jeff opened this issue Jan 25, 2019 · 4 comments
Open

Comments

@Seeker-jeff
Copy link

Dear Professor, I want to implement a fault-tolerant routing algorithm for link failure in NoC, like FADyAD, FoN. But I don't know how to set the link failure rate in Noxim and don't know how to detect these faulty links. Can you give me some advice and methods?

@van-namdinh
Copy link

I also care about this issue! Hope you can find a solution for it!

@Seeker-jeff
Copy link
Author

Hello!For these fault-tolerant routing algorithms such as FoN, it is actually link fault-tolerant routing algorithms. In previous questions, it was mentioned that a faulty network needed a corresponding fault-tolerant routing algorithm. We can skip error detection. We use the flag bit to directly mark the faulty link in the network (the W/E/S/N port of the routing node).This method can be implemented in Noxim with an array or by adding a unit to a class. Then, according to the flag of the node, the routing algorithm judges the fault of the node's W/E/S/N direction and selects the fault-free link route. In this way, these routing algorithms of FoN can be implemented. These are some of the suggestions put forward, and I also hope to discuss them with you.

@van-namdinh
Copy link

irect

Dear Seeker-jeff.
Could you explain and discuss more about the implementation of FoN?
Thanks!

@ishakhari
Copy link

I am also looking for a solution to deactivate a link or a node in Noxim

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

3 participants