FreeRTOS Support Archive
The FreeRTOS support forum is used to obtain active support directly from Real
Time Engineers Ltd. In return for using our top quality software and services for
free, we request you play fair and do your bit to help others too! Sign up
to receive notifications of new support topics then help where you can.
This is a read only archive of threads posted to the FreeRTOS support forum.
The archive is updated every week, so will not always contain the very latest posts.
Use these archive pages to search previous posts. Use the Live FreeRTOS Forum
link to reply to a post, or start a new support thread.
[FreeRTOS Home] [Live FreeRTOS Forum] [FAQ] [Archive Top] [May 2017 Threads] Question about Preemptive SchedulerPosted by leesp on May 23, 2017 Can a task be pre-empted at any point? For example the task below: Can it be pre-empted any time, or pre-emption can only happen while it is waiting for the semaphore?
~~~
static void taskconsole(void *p)
{
(void)p;
for (;;) {
...
... // Can it be pre-empted here?
...
if (xSemaphoreTake(dispmutex, ~0)) { // Or, pre-emption can only happen here?
strwrite(str);
xSemaphoreGive(dispmutex);
}
}
}
~~~
Question about Preemptive SchedulerPosted by rtel on May 24, 2017 In the code you show the task can be preempted at any time other than a few short critical sections that are inside inside the xSempareTake() and xSemaphoreGive() functions.
Question about Preemptive SchedulerPosted by leesp on May 24, 2017 I read the Example 1 found in FreeRTOS book: two tasks are created with SAME priority, and each task will print a different string on the console. It was mentioned that:
> "...both tasks are rapidly entering and exiting the Running state...To be able to select the next task to run, the scheduler itself must execute at the end of each time slice. A periodic interrupt, called the tick interrupt, is used for this purpose"
If configTICKRATEHZ is 1000 (ie 1ms period), but each task's for(;;) loop takes 20ms for example, will the scheduler pre-empt a task every 1ms? Which means a task will be switched in and out 10 times before it complete one loop? Or, the scheduler will wait for a task to complete 1 loop, then pre-empt it?
Question about Preemptive SchedulerPosted by richard_damon on May 24, 2017 If you have enabled both Preempton and Time Slicing, then every tick interrupt you will switch between two equal priority execution bound tasks. The tick interrupt (which is what initiates the switch, know nothing of the loop in the task.
Copyright (C) Amazon Web Services, Inc. or its affiliates. All rights reserved.
|