User: Password:
Subscribe / Log in / New account



Posted Apr 12, 2012 19:24 UTC (Thu) by dlang (subscriber, #313)
In reply to: SCHED_DEADLINE returns by flok
Parent article: SCHED_DEADLINE returns

two problems

1. how can the application know this? (the time will vary depending on how well caching works)

2. what do you do with an application that ends up using more than it claimed it would?

(Log in to post comments)


Posted Apr 12, 2012 19:39 UTC (Thu) by corbet (editor, #1) [Link]

Of course, deadline scheduling depends on exactly this: an application must declare a worst-case execution time along with its deadline. Knowing what the WCET should be is, of course, not a small problem; it's currently fodder for a number of academic careers, I think. Usual practice, I suspect, is to determine it empirically.

As for what happens if you blow the WCET: the deadline scheduler just freezes you out until the next scheduling period starts.

Copyright © 2017, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds