Re: Questions regarding Synchronisation in Windows (Spinlocks)
- From: "Alexander Grigoriev" <alegr@xxxxxxxxxxxxx>
- Date: Mon, 10 Mar 2008 08:02:08 -0700
1) spinlocks used to have different implementation in uniprocessor kernel.
Vista/Longhorn now only ship multiprocessor kernel.
Interrupts are handled in context of ISR. There is no thread switch, as they
don't run in a particular thread context.
"smawsk" <sk.smawsk@xxxxxxxxx> wrote in message
news:b2a63809-b597-4a8c-a8f4-efc069b3a05b@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Hi,
I have some questions regarding the implementation of synchronisatio
techniques in Windows.
I would be greatful if some one can answer these.
1) How are Spinlocks implemented in Windows for a UNIPROCESSOR
machine? Do they involve busy waiting?
Since Spinlocks execute at DPC/Dispatch level, there is no way for the
thread to move to wait state.
Consider a scenario where a thread is trying to acquire a spin lock.
But an interrupt occurs which has an IRQL > DPC Dispatch level OR the
IRQL of the thread that acquired the spin lock. For the new interrupt
to be serviced, dispatcher has to be invoked to switch to the new
thread servicing the interrupt.
What happens in this scenario?
2) What is the difference between an executive object and a kernel
object? Can some one give an example for each?
I reckon Semaphore, Event, Mutex etc are executive objects. So what
kernel objects are these executive objects built on?
Which category do "Dispatcher" objects belong to?
3) What is th edifference between a Mutex and Fast Mutex/Guarded
Mutex?
Thanks in advance.
Warm Regards.
.
- Follow-Ups:
- References:
- Prev by Date: Re: Stack overflow
- Next by Date: Re: How does Taskman know a process is 32 or 64 bit?
- Previous by thread: Questions regarding Synchronisation in Windows (Spinlocks)
- Next by thread: Re: Questions regarding Synchronisation in Windows (Spinlocks)
- Index(es):
Relevant Pages
|
