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

Arbitration #78

Open
SheriefHeshmat opened this issue Nov 27, 2018 · 2 comments
Open

Arbitration #78

SheriefHeshmat opened this issue Nov 27, 2018 · 2 comments

Comments

@SheriefHeshmat
Copy link

Hi All
if i want to change the way of arbitration in noxim , what classes i need to modify in it ?.
and how to assure the work is done correct
cause after modifying in Router and Buffer classes.. nothing appears as output so this is sure that i did something wrong or extra work is needed for sure. so for a quick guidance
thanks a lot

@davidepatti
Copy link
Owner

Please be more precise, give a practical example....

@SheriefHeshmat
Copy link
Author

ok assuming that i have 4 virtual channels and 484 mesh topology and a packet will be transmitted from router [0] to router [9]
the default state in Noxim is that if the header is assigned to VC=2 from the the processing element of router[0] it will be transmitted to other router (regardless to the routing algorithm) to VC= 2 in any router.
i had modified some code inside Router.c and Buffer.c classes, so as not to be restricted the a specific virtual channel. but after the simulation is complete i noticed that the amount of received packets and flits is very small although i am sure the packets reach their destination for deep tracing inside the routing function.
so it seems i need to modify more code to be working efficiently..
that was my question what other classes i need to edit, or how the default cycle for transmitting a packet walk through the noxim simulator..
thanks a lot for helping

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

2 participants