From: "Dmitry A. Kazakov" <mailbox@dmitry-kazakov.de>
Subject: Re: timer_server triggers Task_Termination handler
Date: Fri, 22 Apr 2016 15:42:03 +0200
Date: 2016-04-22T15:42:03+02:00 [thread overview]
Message-ID: <nfd9o4$105j$1@gioia.aioe.org> (raw)
In-Reply-To: nfd91h$6qo$1@dont-email.me
On 22/04/2016 15:33, G.B. wrote:
> On 22.04.16 14:55, Dmitry A. Kazakov wrote:
>> The point is that it must be your scheduler to make sense. You scheduler
>> will be able to know that.
>
> What does "your" stand for and what ownership relation exists
> between the program, the scheduler (whose), and run-time tasks'
> termination events?
The schedule is the master of these tasks. The point is that events must
be reported to the task's master. That eliminates the problem of
ambiguity which tasks, threads, services, drivers, interrupts, embedded
procedures, co-routines etc must generate events.
--
Regards,
Dmitry A. Kazakov
http://www.dmitry-kazakov.de
next prev parent reply other threads:[~2016-04-22 13:42 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-21 10:23 timer_server triggers Task_Termination handler Per Dalgas Jakobsen
2016-04-21 18:14 ` Anh Vo
2016-04-21 18:20 ` Jacob Sparre Andersen
2016-04-21 18:31 ` Anh Vo
2016-04-21 21:13 ` Randy Brukardt
2016-04-22 5:41 ` J-P. Rosen
2016-04-22 6:46 ` Jacob Sparre Andersen
2016-04-21 21:26 ` Robert A Duff
2016-04-22 6:36 ` Georg Bauhaus
2016-04-22 7:25 ` Dmitry A. Kazakov
2016-04-22 10:05 ` G.B.
2016-04-22 12:55 ` Dmitry A. Kazakov
2016-04-22 13:33 ` G.B.
2016-04-22 13:42 ` Dmitry A. Kazakov [this message]
2016-04-22 22:31 ` Randy Brukardt
2016-04-23 9:55 ` Dmitry A. Kazakov
2016-04-25 21:42 ` Randy Brukardt
2016-04-22 22:35 ` Randy Brukardt
replies disabled
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox