1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
|
/*=========================================================================
Program: Insight Segmentation & Registration Toolkit
Module: $RCSfile: itkFastMutexLock.h,v $
Language: C++
Date: $Date: 2006-03-06 15:07:34 $
Version: $Revision: 1.19 $
Copyright (c) Insight Software Consortium. All rights reserved.
See ITKCopyright.txt or http://www.itk.org/HTML/Copyright.htm for details.
Portions of this code are covered under the VTK copyright.
See VTKCopyright.txt or http://www.kitware.com/VTKCopyright.htm for details.
This software is distributed WITHOUT ANY WARRANTY; without even
the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR
PURPOSE. See the above copyright notices for more information.
=========================================================================*/
#ifndef __itkFastMutexLock_h
#define __itkFastMutexLock_h
#include "itkObject.h"
#include "itkSimpleFastMutexLock.h"
#include "itkObjectFactory.h"
namespace itk
{
/** \class FastMutexLock
* \brief Critical section locking class.
*
* FastMutexLock allows the locking of variables which are accessed
* through different threads. This header file also defines
* SimpleFastMutexLock which is not a subclass of Object.
* The API is identical to that of MutexLock, and the behavior is
* identical as well, except on Windows 9x/NT platforms. The only difference
* on these platforms is that MutexLock is more flexible, in that
* it works across processes as well as across threads, but also costs
* more, in that it evokes a 600-cycle x86 ring transition. The
* FastMutexLock provides a higher-performance equivalent (on
* Windows) but won't work across processes. Since it is unclear how,
* in itk, an object at the itk level can be shared across processes
* in the first place, one should use FastMutexLock unless one has
* a very good reason to use MutexLock. If higher-performance equivalents
* for non-Windows platforms (Irix, SunOS, etc) are discovered, they
* should replace the implementations in this class
*
* \ingroup OSSystemObjects
*/
class ITKCommon_EXPORT FastMutexLock : public Object
{
public:
/** Standard class typedefs. */
typedef FastMutexLock Self;
typedef Object Superclass;
typedef SmartPointer<Self> Pointer;
typedef SmartPointer<const Self> ConstPointer;
/** Method for creation. */
itkNewMacro(Self);
/** Run-time type information. */
itkTypeMacro(FastMutexLock,Object);
/** Lock the itkFastMutexLock. */
void Lock();
/** Unlock the FastMutexLock. */
void Unlock();
protected:
FastMutexLock() {}
~FastMutexLock() {}
SimpleFastMutexLock m_SimpleFastMutexLock;
void PrintSelf(std::ostream& os, Indent indent) const;
private:
FastMutexLock(const Self&); //purposely not implemented
void operator=(const Self&); //purposely not implemented
};
inline void FastMutexLock::Lock( void )
{
m_SimpleFastMutexLock.Lock();
}
inline void FastMutexLock::Unlock( void )
{
m_SimpleFastMutexLock.Unlock();
}
}//end itk namespace
#endif
|
