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
使用锁定实现计数器和互斥
