[This is a preview of an interface that may appear in future releases of Windows.]
The InitializeCriticalSectionAndSpinCount function initializes a critical section object and sets the spin count for the critical section.
BOOL InitializeCriticalSectionAndSpinCount(
|
LPCRITICAL_SECTION lpCriticalSection, |
// pointer to critical section |
|
DWORD dwSpinCount |
// spin count for critical section |
|
); |
If the function succeeds, the return value is nonzero.
If the function fails, the return value is zero. To get extended error information, call GetLastError.
The threads of a single process can use a critical section object for mutual-exclusion synchronization. The process is responsible for allocating the memory used by a critical section object, which it can do by declaring a variable of type CRITICAL_SECTION. Before using a critical section, some thread of the process must call the InitializeCriticalSection or InitializeCriticalSectionAndSpinCount function to initialize the object. You can subsequently modify the spin count by calling the SetCriticalSectionSpinCount function.
The spin count is useful for critical sections of short duration that can experience high levels of contention. Consider a worst-case scenario, in which an application on an SMP system has two or three threads constantly allocating and releasing memory from the heap. The application serializes the heap with a critical section. In the worst-case scenario, contention for the critical section is constant, and each thread makes an expensive call to the WaitForSingleObject function. However, if the spin count is set properly, the calling thread will not immediately call WaitForSingleObject when contention occurs. Instead, the calling thread can acquire ownership of the critical section if it is released during the spin operation.
You can improve performance significantly by choosing a small spin count for a critical section of short duration. The Windows NT heap manager uses a spin count of roughly 4000 for its per-heap critical sections. This gives great performance and scalability in almost all worst-case scenarios.
InitializeCriticalSection, SetCriticalSectionSpinCount, WaitForSingleObject