hi, experts.
I have a question about SetEvent().
Will SetEvent() triger the system scheduler regardless whether there is a
system_tick event or not?
I mean will SetEvent() wake up WaitforSingleObject immediately? Or it just
makes that event singled and goes on until it runs out its time-slice and
then the scheduler wake up WaitforSingleObject?

Re: SetEvent and Schedule by make

make
Tue Jul 25 04:11:49 CDT 2006

I think only system_tick event and the thread is scheduled,then wake up the
thread.
"simon" <simon@discussions.microsoft.com> wrote in message
news:D9A03F89-AEB8-4687-BD3A-D0D8184D9D40@microsoft.com...
> hi, experts.
> I have a question about SetEvent().
> Will SetEvent() triger the system scheduler regardless whether there is a
> system_tick event or not?
> I mean will SetEvent() wake up WaitforSingleObject immediately? Or it just
> makes that event singled and goes on until it runs out its time-slice and
> then the scheduler wake up WaitforSingleObject?



Re: SetEvent and Schedule by Remi

Remi
Tue Jul 25 04:36:17 CDT 2006

SetEvent is immediately active, provided no other thread with better
priority is running.
This is quite normal for a Real-Time OS, specially when the
interrupt-processing scheme usually involves signaling an event to wake-up
an Interrupt Service Thread (IST.)
HTH
Remi

"simon" <simon@discussions.microsoft.com> a écrit dans le message de news:
D9A03F89-AEB8-4687-BD3A-D0D8184D9D40@microsoft.com...
> hi, experts.
> I have a question about SetEvent().
> Will SetEvent() triger the system scheduler regardless whether there is a
> system_tick event or not?
> I mean will SetEvent() wake up WaitforSingleObject immediately? Or it just
> makes that event singled and goes on until it runs out its time-slice and
> then the scheduler wake up WaitforSingleObject?