Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
EPOS EPOS
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 10
    • Issues 10
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Operations
    • Operations
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Repository
    • Value Stream
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • EPOS Developers
  • EPOSEPOS
  • Issues
  • #9

Closed
Open
Created Jan 30, 2020 by José Luis Conradi Hoffmann@hoffmannMaintainer

EDF Priority update

The current implementation of priority as an int incur that long runs using EDF scheduling will generate priority inversion, thus a thread that reaches a negative priority will be the highest priority of the system, generating a run-time bug. However, modifying the type of priority to be related to the Life_Span Traits when using EDF (and its derivatives) will generate a lot of overhead when using a 64bits attribute in a 32bits architecture, due to the high frequency of scheduling operations. A new way to reset the priority count should be provided.

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking