#3732 closed task (fixed)
Add rtems_scheduler_get_processor_maximum()
Reported by: | Sebastian Huber | Owned by: | Sebastian Huber |
---|---|---|---|
Priority: | normal | Milestone: | 5.1 |
Component: | rtems | Version: | 5 |
Severity: | normal | Keywords: | qualification |
Cc: | Blocked By: | ||
Blocking: | #3990 |
Description (last modified by Sebastian Huber)
Add rtems_scheduler_get_processor_maximum() as a replacement for rtems_get_processor_count(). The rtems_get_processor_count() is a bit orphaned. Adopt it by the Scheduler Manager. The count is also misleading, since the processor set may have gaps and the actual count of online processors may be less than the value returned by rtems_get_processor_count().
Change History (7)
comment:1 Changed on 04/05/19 at 06:17:36 by Sebastian Huber
Description: | modified (diff) |
---|---|
Summary: | Add rtems_scheduler_get_maximum_processor() → Add rtems_scheduler_get_processor_maximum() |
comment:2 Changed on 04/09/19 at 06:11:52 by Sebastian Huber <sebastian.huber@…>
comment:3 Changed on 04/09/19 at 06:13:08 by Sebastian Huber <sebastian.huber@…>
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
comment:6 Changed on 05/28/20 at 13:29:14 by Sebastian Huber
Blocking: | 3990 added |
---|
comment:7 Changed on 06/23/21 at 07:16:03 by Sebastian Huber
Keywords: | qualification added |
---|
Note: See
TracTickets for help on using
tickets.
In f9219db/rtems: