mutexes
美 
英
例句
Imagine, if you will, a pair of mutexes; we'll call them count_mutex and rand_mutex.
想像這兒有兩個互斥量，我們分別稱它們為count_mutex和rand_mutex。
OK, now it's time to see all the different ways to use mutexes.
現在該來看看使用互斥對象的各種不同方法了。
So far, you have used a mutex or multiple mutexes included as part of the data structure for synchronization.
到目前為止，都是在數據結構中使用一個或多個互斥鎖管理同步。
Mutexes will insert a "memory barrier, " which ensures that the writes to main memory occur in the order the threads lock the mutex.
互斥對象將插入一道“內存關卡”，由它來確保對主存的寫入按照線程鎖定互斥對象的順序進行。
pthread_mutexes can be created with different locking policies.
pthread_mutex可以使用不同的鎖定策略創建。
Deadlock can also happen if threads do not unlock mutexes properly.
如果線程沒有正確的釋放互斥，死鎖也會發生。
Mutexes provide mutual exclusion for one or more data objects and are the primary method of thread synchronization.
互斥體能讓一個或多個數據對象相互排斥。互斥體是線程同步的主要手段。
But parallel computing is more than just using mutexes and condition variables in random functions and methods.
但是，并行編程不只是在隨便什么函數和方法中使用互斥鎖和條件變量。
Robust mutexes solve the problem of cleaning up locks properly after an application holding locks crashes.
健壯的互斥鎖解決了在持有鎖的應用程序崩潰后正確清理鎖的問題。
An important problem associated with mutexes is the possibility of deadlock.
一個和互斥有關的重要問題是可能發生的死鎖。
You should have a basic understanding of thread creation, mutexes, and condition variables, as well.
您還應該基本了解線程的創建、互斥鎖和條件變量。
Finally, we explore kernel mutexes, which are built on top of the atomic API.
最后，我們討論構建在原子API上的內核互斥鎖。
Mutexes are available in the kernel as a way to accomplish semaphore behavior.
在內核中可以使用互斥鎖來實現信號量行為。
Linux pthread mutexes are supported by fast user-space mutexes, known as futexes.
快速用戶空間互斥（也被稱為futexes）支持Linuxpthread互斥鎖。
Almost free as code size, you need no semaphores nor mutexes. * Almost free as code size, you need no semaphores nor mutexes.
基本上沒有代碼空間開銷，你不需要信號量或互斥鎖。
For achieving synchronization, you can use mutexes.
要實現同步，您可以使用互斥信號量。
First of all, mutexes are used to serialize access to *shared data*.
首先，互斥對象是用于串行化存取*共享數據*。
I added mutexes to the shared data structures and add locks to most methods.
我為共享的數據結構增加了互斥體，還給大多數方法上了鎖。
The most common building blocks of intertask communication are semaphores and mutexes.
大進程間通訊的的基石是信號燈和互斥。
Mutexes are system-wide objects which multiple processes can see.
互斥是系統范圍內對象，可以由多個進程使用。
Thus no mutexes are held by the signal while a slot is executing.
因此，當插槽執行時，信號并沒有持有互斥體。
But mutexes are faster and more compact than the current kernel semaphore option, so if they fit your need, they're the choice to use.
但是互斥鎖比當前的內核信號量選項更快，并且更加緊湊，因此如果它們滿足您的需求，那么它們將是您明智的選擇。
Part 3 covers mutexes, critical sections, and wait functions.
第3部分涵蓋了信號量、關鍵區域和等待函數。
These mutexes are not visible to Java code, only VM C code.
這些互斥量只對VM的C代碼可見。
I've used a combination of mutexes and spinlocks to keep things synchronized.
我使用互斥體和自旋鎖（spinlock）的組合方案來保證同步。
Higher-level interfaces enable much simpler code, even if there are still mutexes and such under the covers.
高級別的接口可以簡化代碼，即使仍然有互斥這一類的東西。
Another problem with mutexes is that contention for a mutex can lead to priority inversion.
另外一個問題是互斥鎖的爭奪會造成優先權倒置。
To produce predictable code, you'll want to use mutexes.
要產生可預測的代碼，應使用互斥對象。
The most commo building lock of intertask communication are semaphore and mutexes.
大部分進程間通訊的建立的基石是信號燈和互斥。
If you place too many mutexes, your code won't have any kind of concurrency and will run slower than a single-threaded solution.
如果放置了過多的互斥對象，代碼就沒有什么并發性可言，運行起來也比單線程解決方案慢。
Mutexes are necessary tools for threaded programs, but they can't do everything.
互斥對象是線程程序必需的工具，但它們并非萬能的。
The decision about which mutexes to lock is made based on data only available at runtime. This is the essence of the problem.
應該鎖定哪些互斥量取決于僅在運行時可用的數據，這是問題的關鍵所在。
As with mutexes, it's possible that these calls won't do very much in some implementations, but you should make them anyway.
對于互斥量來說，這些調用在有些實現中可能并不做什么，但是您也應該調用它們。
This is how mutexes work.
互斥對象是這樣工作的。
Implementing counters and mutexes with locking
使用鎖定實現計數器和互斥
