Searched hist:"813 d4cbe94b99e33ac2b921ae76df4d1b2b39b40" (Results 1 – 8 of 8) sorted by relevance
| /haiku/headers/private/system/ |
| H A D | user_mutex_defs.h | 813d4cbe94b99e33ac2b921ae76df4d1b2b39b40 Sun Apr 11 16:07:39 UTC 2010 Ingo Weinhold <ingo_weinhold@gmx.de> * Moved created subdirectory src/system/kernel/lock.cpp to new subdirectory
locks.
* Added syscalls for a new kind of mutex. A mutex consists only of an int32 and
doesn't require any kernel resources. So it's initialization cannot fail
(it consists only of setting the mutex value to 0). An uncontended lock or
unlock operation can basically consist of an atomic_*() in userland. The
syscalls (when the mutex is contended) are a bit more expensive than semaphore
operations, though.
git-svn-id: file:///srv/svn/repos/haiku/haiku/trunk@36158 a95241bf-73f2-0310-859d-f6bbb57e9c96
|
| H A D | syscalls.h | 813d4cbe94b99e33ac2b921ae76df4d1b2b39b40 Sun Apr 11 16:07:39 UTC 2010 Ingo Weinhold <ingo_weinhold@gmx.de> * Moved created subdirectory src/system/kernel/lock.cpp to new subdirectory
locks.
* Added syscalls for a new kind of mutex. A mutex consists only of an int32 and
doesn't require any kernel resources. So it's initialization cannot fail
(it consists only of setting the mutex value to 0). An uncontended lock or
unlock operation can basically consist of an atomic_*() in userland. The
syscalls (when the mutex is contended) are a bit more expensive than semaphore
operations, though.
git-svn-id: file:///srv/svn/repos/haiku/haiku/trunk@36158 a95241bf-73f2-0310-859d-f6bbb57e9c96
|
| /haiku/headers/private/kernel/ |
| H A D | user_mutex.h | 813d4cbe94b99e33ac2b921ae76df4d1b2b39b40 Sun Apr 11 16:07:39 UTC 2010 Ingo Weinhold <ingo_weinhold@gmx.de> * Moved created subdirectory src/system/kernel/lock.cpp to new subdirectory
locks.
* Added syscalls for a new kind of mutex. A mutex consists only of an int32 and
doesn't require any kernel resources. So it's initialization cannot fail
(it consists only of setting the mutex value to 0). An uncontended lock or
unlock operation can basically consist of an atomic_*() in userland. The
syscalls (when the mutex is contended) are a bit more expensive than semaphore
operations, though.
git-svn-id: file:///srv/svn/repos/haiku/haiku/trunk@36158 a95241bf-73f2-0310-859d-f6bbb57e9c96
|
| /haiku/src/system/kernel/locks/ |
| H A D | user_mutex.cpp | 813d4cbe94b99e33ac2b921ae76df4d1b2b39b40 Sun Apr 11 16:07:39 UTC 2010 Ingo Weinhold <ingo_weinhold@gmx.de> * Moved created subdirectory src/system/kernel/lock.cpp to new subdirectory
locks.
* Added syscalls for a new kind of mutex. A mutex consists only of an int32 and
doesn't require any kernel resources. So it's initialization cannot fail
(it consists only of setting the mutex value to 0). An uncontended lock or
unlock operation can basically consist of an atomic_*() in userland. The
syscalls (when the mutex is contended) are a bit more expensive than semaphore
operations, though.
git-svn-id: file:///srv/svn/repos/haiku/haiku/trunk@36158 a95241bf-73f2-0310-859d-f6bbb57e9c96
|
| H A D | lock.cpp | 813d4cbe94b99e33ac2b921ae76df4d1b2b39b40 Sun Apr 11 16:07:39 UTC 2010 Ingo Weinhold <ingo_weinhold@gmx.de> * Moved created subdirectory src/system/kernel/lock.cpp to new subdirectory
locks.
* Added syscalls for a new kind of mutex. A mutex consists only of an int32 and
doesn't require any kernel resources. So it's initialization cannot fail
(it consists only of setting the mutex value to 0). An uncontended lock or
unlock operation can basically consist of an atomic_*() in userland. The
syscalls (when the mutex is contended) are a bit more expensive than semaphore
operations, though.
git-svn-id: file:///srv/svn/repos/haiku/haiku/trunk@36158 a95241bf-73f2-0310-859d-f6bbb57e9c96
|
| /haiku/src/system/kernel/ |
| H A D | syscalls.cpp | 813d4cbe94b99e33ac2b921ae76df4d1b2b39b40 Sun Apr 11 16:07:39 UTC 2010 Ingo Weinhold <ingo_weinhold@gmx.de> * Moved created subdirectory src/system/kernel/lock.cpp to new subdirectory
locks.
* Added syscalls for a new kind of mutex. A mutex consists only of an int32 and
doesn't require any kernel resources. So it's initialization cannot fail
(it consists only of setting the mutex value to 0). An uncontended lock or
unlock operation can basically consist of an atomic_*() in userland. The
syscalls (when the mutex is contended) are a bit more expensive than semaphore
operations, though.
git-svn-id: file:///srv/svn/repos/haiku/haiku/trunk@36158 a95241bf-73f2-0310-859d-f6bbb57e9c96
|
| H A D | main.cpp | 813d4cbe94b99e33ac2b921ae76df4d1b2b39b40 Sun Apr 11 16:07:39 UTC 2010 Ingo Weinhold <ingo_weinhold@gmx.de> * Moved created subdirectory src/system/kernel/lock.cpp to new subdirectory
locks.
* Added syscalls for a new kind of mutex. A mutex consists only of an int32 and
doesn't require any kernel resources. So it's initialization cannot fail
(it consists only of setting the mutex value to 0). An uncontended lock or
unlock operation can basically consist of an atomic_*() in userland. The
syscalls (when the mutex is contended) are a bit more expensive than semaphore
operations, though.
git-svn-id: file:///srv/svn/repos/haiku/haiku/trunk@36158 a95241bf-73f2-0310-859d-f6bbb57e9c96
|
| H A D | Jamfile | 813d4cbe94b99e33ac2b921ae76df4d1b2b39b40 Sun Apr 11 16:07:39 UTC 2010 Ingo Weinhold <ingo_weinhold@gmx.de> * Moved created subdirectory src/system/kernel/lock.cpp to new subdirectory
locks.
* Added syscalls for a new kind of mutex. A mutex consists only of an int32 and
doesn't require any kernel resources. So it's initialization cannot fail
(it consists only of setting the mutex value to 0). An uncontended lock or
unlock operation can basically consist of an atomic_*() in userland. The
syscalls (when the mutex is contended) are a bit more expensive than semaphore
operations, though.
git-svn-id: file:///srv/svn/repos/haiku/haiku/trunk@36158 a95241bf-73f2-0310-859d-f6bbb57e9c96
|