Hi! On Mon, 15 Feb 2010, Mido wrote:
> Would it be possible that an interrupt is triggered during the execution of > an event (e.g. fired), and that interrupt posts a task that will signal the > next event before the current event completes? > > For example, if a timer has a very high frequency, and the fired() event is > doing long processing. > As you said, an interrupt handler usually is very short and it posts a task. That task usually signals the appropriate events. While this task is executed it is possible that the original interrupt is fired again. The task will be interrupted, the task handler will be executed and the task will be scheduled again for execution. -- Razvan ME > -----Original Message----- > From: [email protected] > [mailto:[email protected]] On Behalf Of Razvan > Musaloiu-E. > Sent: Monday, February 15, 2010 2:48 AM > To: Arik Sapojnik > Cc: Tinyos-help > Subject: Re: [Tinyos-help] Tasks and interrupts > > Hi! > > On Wed, 10 Feb 2010, Arik Sapojnik wrote: > >> Hello, >> >> I'm trying to understand the interrupts in TinyOS. >> It looks like even when an interrupt is occurred (for instance a timer), it >> only posts the desired task (for instance Timer.fired() ) to be executed >> somewhere in the future. >> Hence the interrupt preempts the task only to post it's task (a VERY short >> period of time). >> Is it really so? >> > > Yes, that is correct. > > -- Razvan ME > _______________________________________________ Tinyos-help mailing list [email protected] https://www.millennium.berkeley.edu/cgi-bin/mailman/listinfo/tinyos-help
