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

FLIN scheduler #36

Open
sac2019 opened this issue Dec 18, 2019 · 6 comments
Open

FLIN scheduler #36

sac2019 opened this issue Dec 18, 2019 · 6 comments

Comments

@sac2019
Copy link

sac2019 commented Dec 18, 2019

hi

does the MQSim support the FLIN scheduler?
why the .c and .h file of FLIN are commented in the source code of simulator?

Regards

@sac2019
Copy link
Author

sac2019 commented Apr 15, 2020

@arashta

@HrithikSampson
Copy link

Maybe because flin reduces performance

@arashta
Copy link
Collaborator

arashta commented Apr 28, 2020

Hello @sac2019 and @HrithikSampson,
The FLIN source code was prepared before the official release of MQSim. The FLIN source should be refactored to be able to work with the current version of MQSim which has been majorly refactored and boosted with new features after the release.

@HrithikSampson
Copy link

HrithikSampson commented Apr 28, 2020 via email

@HrithikSampson
Copy link

HrithikSampson commented Apr 28, 2020 via email

@sac2019
Copy link
Author

sac2019 commented Apr 30, 2020

Sir , Though,I am just an undergraduate student who read the code but I think if in nvm_transaction_flash.cpp if you change the constructor parameter corresponding to bool FLIN_barrier to true and carefully uncomment the code in tsu flin .h and .CPP it might work

On Tue, 28 Apr, 2020, 11:08 PM Arash Tavakkol, @.***> wrote: Hello @sac2019 https://github.com/sac2019 and @HrithikSampson https://github.com/HrithikSampson, The FLIN source code was prepared before the official release of MQSim. The FLIN source should be refactored to be able to work with the current version of MQSim which has been majorly refactored and boosted with new features after the release. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#36 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/ANLNWAZ5BDMN4CRS6R23TJLRO4IAJANCNFSM4J4M6HKA .

it doesn't work....

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