Mirrors_Framework/nuttx
1
0
Fork 0
mirror of https://github.com/apache/nuttx.git synced 2026-02-06 04:22:26 +08:00
Code Issues Actions Packages Projects Releases Wiki Activity

sched: Simplify the interval adjustment in nxsched_timer_start.

Browse Source 
This commit simplified the interval adjustment in nxsched_timer_start.

Signed-off-by: ouyangxiangzhen <ouyangxiangzhen@xiaomi.com>
This commit is contained in:
ouyangxiangzhen
2025-12-25 10:10:20 +08:00
committed by Xiang Xiao
parent 6300bc5522
commit 299ece7cbe
1 changed files with 27 additions and 20 deletions
Download Patch File Download Diff File Expand all files Collapse all files

47
sched/sched/sched_timerexpiration.c
View File

@@ -108,6 +108,32 @@ static unsigned int g_timernested;
* Private Functions
****************************************************************************/
static inline_function clock_t adjust_next_interval(clock_t interval)
{
clock_t ret = interval;
#ifdef CONFIG_SCHED_TICKLESS_LIMIT_MAX_SLEEP
ret = MIN(ret, g_oneshot_maxticks);
#endif
/* Normally, timer event cannot triggered on exact time due to the
* existence of interrupt latency.
* Assuming that the interrupt latency is distributed within
* [Best-Case Execution Time, Worst-Case Execution Time],
* we can set the timer adjustment value to the BCET to reduce the latency.
* After the adjustment, the timer interrupt latency will be
* [0, WCET - BCET].
* Please use this carefully, if the timer adjustment value is not the
* best-case interrupt latency, it will immediately fired another timer
* interrupt, which may result in a much larger timer interrupt latency.
*/
ret = ret <= (CONFIG_TIMER_ADJUST_USEC / USEC_PER_TICK) ? 0 :
ret - (CONFIG_TIMER_ADJUST_USEC / USEC_PER_TICK);
return ret;
}
static inline_function clock_t get_time_tick(void)
{
#ifdef CONFIG_SYSTEM_TIME64
@@ -390,26 +416,7 @@ static clock_t nxsched_timer_start(clock_t ticks, clock_t interval)
if (interval != CLOCK_MAX)
{
#ifdef CONFIG_SCHED_TICKLESS_LIMIT_MAX_SLEEP
interval = MIN(interval, g_oneshot_maxticks);
#endif
/* Normally, timer event cannot triggered on exact time
* due to the existence of interrupt latency.
* Assuming that the interrupt latency is distributed within
* [Best-Case Execution Time, Worst-Case Execution Time],
* we can set the timer adjustment value to the BCET to
* reduce the latency.
* After the adjustment, the timer interrupt latency will be
* [0, WCET - BCET].
* Please use this carefully, if the timer adjustment value is not
* the best-case interrupt latency, it will immediately fired
* another timer interrupt, which may result in a much larger timer
* interrupt latency.
*/
interval = interval <= (CONFIG_TIMER_ADJUST_USEC / USEC_PER_TICK) ? 0 :
interval - (CONFIG_TIMER_ADJUST_USEC / USEC_PER_TICK);
interval = adjust_next_interval(interval);
#ifdef CONFIG_SCHED_TICKLESS_ALARM
/* Convert the delay to a time in the future (with respect