diff options
| author | rpj <rpj> | 2006-12-22 02:36:40 +0000 |
|---|---|---|
| committer | rpj <rpj> | 2006-12-22 02:36:40 +0000 |
| commit | 9e61bc0571b4812381cf89dd6f4bcbe3931f6acd (patch) | |
| tree | 2b60eec9340369ed259a9d1de422ac5ec3eb9291 /ptw32_MCS_lock.c | |
| parent | 1beb00e609d241ee6c2048c476e2240f05033cbd (diff) | |
Diffstat (limited to 'ptw32_MCS_lock.c')
| -rw-r--r-- | ptw32_MCS_lock.c | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/ptw32_MCS_lock.c b/ptw32_MCS_lock.c index 478a059..1a143ea 100644 --- a/ptw32_MCS_lock.c +++ b/ptw32_MCS_lock.c @@ -50,8 +50,8 @@ * operations required to add or remove nodes from the queue do not trigger * cache-coherence updates. * - * Like 'named' mutexes, MCS locks consume system recourses transiently - - * they are able to acquire and free recourses automatically - but MCS + * Like 'named' mutexes, MCS locks consume system resources transiently - + * they are able to acquire and free resources automatically - but MCS * locks do not require any unique 'name' to identify the lock to all * threads using it. * |