Skip to content

feat(edf): prepare for alternative deadline computations - #812

Open
romancardenas wants to merge 1 commit into
tier4:mainfrom
romancardenas:dag/configurable_deadline_edf
Open

romancardenas wants to merge 1 commit into
tier4:mainfrom
romancardenas:dag/configurable_deadline_edf

Conversation

@romancardenas

Copy link
Copy Markdown
Contributor

Description

The default policy preserves existing behavior: standalone tasks use wake_time + relative_deadline, and DAG tasks keep the existing job deadline calculation. CPU affinity, wake-time tie-breaking, and the public scheduler API are unchanged.

Related links

How was this PR tested?

  • scripts/ci.sh passes on my machine.

Notes for reviewers

This PR introduces the internal policy hook only. Computing deadlines from per-node DAG latest finish times is deferred to a follow-up.

@romancardenas
romancardenas marked this pull request as ready for review November 19, 2026 03:11
@atsushi421

Copy link
Copy Markdown
Contributor

@romancardenas
I propose to add the ordering by the latest finish time of each node as a new SchedulerType, not as a deadline policy of EDFScheduler.

As we discussed in slack, the latest finish time is a value that the scheduler computes from WCET estimates. It is not a timing requirement of the system. EDF orders jobs by their real deadlines, so ordering by a computed value is a different algorithm. If a node needs its own deadline as a real requirement, register_reactor() must take it as an argument, as register_sink_reactor() does for the sink.

This branch has not been deployed

No deployments
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

Successfully merging this pull request may close these issues.

2 participants