Opened on 05/23/18 at 19:10:36
Closed on 09/17/18 at 11:34:20
#3432 closed enhancement (wontfix)
Remove Simple SMP Priority Scheduler
Reported by: | Joel Sherrill | Owned by: | |
---|---|---|---|
Priority: | normal | Milestone: | 5.1 |
Component: | score | Version: | 5 |
Severity: | normal | Keywords: | |
Cc: | Blocked By: | ||
Blocking: |
Description
This scheduler was the first SMP scheduler added. It was created to have an easy SMP scheduler to debug. This was especially important when all of the SMP modifications and support were new. A Simple Scheduler has a use case as a low resource alternative for small uniprocessor systems. But the SMP variant just doesn't seem to have a good use case. If you have an SMP system, the application is almost certain to have enough resources where the more complicated data structures used by the other schedulers wouldn't be a burden. The Deterministic Priority Scheduler uses ~3K for FIFO with 256 priorities. This should not be an issue for an SMP system.
This ticket is a proposal to remove this as no longer having a use case.
Change History (2)
comment:1 Changed on 05/25/18 at 07:59:43 by Sebastian Huber
comment:2 Changed on 09/17/18 at 11:34:20 by Sebastian Huber
Resolution: | → wontfix |
---|---|
Status: | new → closed |
This scheduler implementation should not be removed. It is useful in clustered scheduler scenarios.
Please don't remove this scheduler. I may change it a bit to support also the simple one-to-one and one-to-all thread processor affinities. It uses very simple data structures which yield a small object code size. Even big SMP machines may have a small L1 cache.