-
Notifications
You must be signed in to change notification settings - Fork 39
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
Two flows with different cycle merge into the same link #27
Comments
Hello. The default strategy for schedule generation uses a strategy that we call "microcyles" which, as you pointed out, generates a cycle of size equals to the greatest common divisor of all flow periods. To use the least common multiple instead, a scheduling strategy that we refer to "hypercycle", after declaring a port of a switch, use the method |
hi,Thank you for your response. I have set the port of switch2 to hypercycle which is connected to dev10 in my example.
Code:
But it doesn't seem to work,the Cycle duration of Switch2 is still 1ms. |
Hi,
Thanks for your code. I am running an example on the project.
My example has two flows as follows:
The topology is:
And the result is:
I notice that Cycle duration of Switch2 is 1ms. It means that there is a slot in 1ms. But cycle of flow0 is 2ms, and cycle of flow1 is 3ms. There will has two slot without packets within every 6ms.
I think it is better that the Cycle duration of Switch2 shall be 6ms (i.e. Least Common Multiple of two flow). In each cycle, there are four time slots .
Which part of the code do I need to modify?
Thanks
The text was updated successfully, but these errors were encountered: