From: Simon Wright <simon@pushface.org>
Subject: Re: Scheduling behaviour issue
Date: Wed, 22 Apr 2020 18:20:22 +0100
Date: 2020-04-22T18:20:22+01:00 [thread overview]
Message-ID: <lyo8rjl9nt.fsf@pushface.org> (raw)
In-Reply-To: 3a224dbe-5af4-4f8a-84d5-03e8b56398fa@googlegroups.com
fabien.chouteau@gmail.com writes:
> On Wednesday, April 22, 2020 at 1:34:53 PM UTC+2, Simon Wright wrote:
>> but FreeRTOS adds the preempted task at the *tail* of its ready queue
>> ([4], section Prioritized Pre-emptive Scheduling (without Time Slicing),
>> on page 95 or thereabouts).
>
> I couldn't find the paragraph that says that.
It's the dicussion after Figure 29.
There are 2 "continuous" tasks (no interaction with the scheduler) of
the same priority, say A & B (this is so unlike any real-time system
I've encountered! You might have just one, doing some sort of
housekeeping or monitoring).
Both A and B are ready. One of the tasks, A, runs until a
higher-priority task C preempts it; when the higher-priority task
finishes, *the other task* B runs!
> That seems very strange to not resume the task that was just
> preempted.
I so agree. I think it's because the mechanism used is derived from
FreeRTOS's round-robin scheduler.
next prev parent reply other threads:[~2020-04-22 17:20 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-22 11:34 Scheduling behaviour issue Simon Wright
2020-04-22 16:16 ` fabien.chouteau
2020-04-22 17:20 ` Simon Wright [this message]
2020-04-22 18:05 ` Anh Vo
2020-04-22 18:21 ` Niklas Holsti
2020-04-22 18:03 ` Niklas Holsti
2020-04-22 20:41 ` AdaMagica
2020-04-22 21:58 ` Niklas Holsti
2020-04-23 0:47 ` Jere
2020-04-23 10:56 ` Simon Wright
2020-04-23 12:38 ` Niklas Holsti
2020-04-23 12:57 ` Niklas Holsti
2020-04-23 11:48 ` Simon Wright
2020-04-23 13:18 ` Niklas Holsti
replies disabled
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox