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

ostest RR scheduler testing #1989

Open
TaiJuWu opened this issue Aug 22, 2023 · 3 comments
Open

ostest RR scheduler testing #1989

TaiJuWu opened this issue Aug 22, 2023 · 3 comments

Comments

@TaiJuWu
Copy link
Contributor

TaiJuWu commented Aug 22, 2023

I have a question about RR scheduler

"If RR scheduling is working, they should start and complete at\n");

The comment shows thread_1 and thread_2 should start and complete at about the same time.
But I did not see any assert condition about it.

Is it needed to modify or it is correct?
I try to add some assert to this problem at
https://github.com/TaiJuWu/nuttx-apps/blob/30038063e2b9958202118d4b4c3724eec7069622/testing/ostest/roundrobin.c#L254
Im not sure it's useful and is this method great?
If anyone can give me some suggestion, I will be very grateful.

@acassis
Copy link
Contributor

acassis commented Oct 18, 2023

@TaiJuWu I think this could be a good idea! We need more people testing RR SCHED. Did you have chance to test RR with Tickeless mode?

@TaiJuWu
Copy link
Contributor Author

TaiJuWu commented Oct 18, 2023

No. I just used nsh:smp as my default setting. I will try using tickless mode this weekend.

@TaiJuWu
Copy link
Contributor Author

TaiJuWu commented Oct 20, 2023

@TaiJuWu I think this could be a good idea! We need more people testing RR SCHED. Did you have chance to test RR with Tickeless mode?

It also can work on qemu-armv8a:nsh_smp_tickless but why we need to use tickless mode?
Actually, I can't image what condition will make this test fail....

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