While Listing 6 shows push_back using the read-write lock.
清单6 给出使用读写锁的 push_back 方法。
The capital W in the FD column indicates that the application has a write lock on the whole file.
FD列中的大写W表示该应用程序具有对整个文件的写锁。
Exclusive lock - is a write lock that prevents data from being changed while a user is already modifying it.
独占式加锁—是一种写加锁，防止数据在有用户已经在修改它时被修改。
Locking occurs on two levels (see Listing 7) : The list has a read-write lock, while individual nodes contain a mutex.
在两个级别上执行锁定(见清单7)：链表有一个读写锁，各个节点包含一个互斥锁。
For example, if you have six databases and one takes a write lock, the other five are still available for read and write.
例如，如果你有六个数据库，其中一个有写锁，其他的五个仍然可以进行读写。
Some file systems support network clients obtaining an exclusive write lock on a file and remove the lock if the client crashes.
一些文件系统支持网络客户端获取对文件的排它写锁定，以及当客户端死机时移交锁定。
After the indexer receives the IASTTranslationUnit, it gets a write lock on the PDOM and begins persisting the TranslationUnit's data.
索引器接收到IASTTranslationUnit后，会得到在PDOM上的一个写锁并开始保持TranslationUnit的数据。
The reason this technique is called the "cheap read-write lock" is that you are using different synchronization mechanisms for reads and writes.
之所以将这种技术称之为 “开销较低的读-写锁” 是因为您使用了不同的同步机制进行读写操作。
The time (microseconds) to perform the transaction for a single node were 1877 with regular locking, 1225 with an explicit write lock, and 181 using a "dirty interface".
完成一个事务的时间（以毫秒计）在单节点上是：常规锁——1877，显式写入锁——1225，而使用“脏接口”的话是181。
If you don't adhere to this approach in prioritizing writer threads using pthread_setschedprio, then given the nature of read-write lock, it is easy to see how writer threads could starve.
如果不按这种方式使用 pthread_setschedprio 设置写线程的优先级，根据读写锁的性质，很容易看出写线程可能会饿死。
With this type of lock, concurrent applications can read from or write to the locked table.
有了这一类型的锁，并发应用程序就可以读或写已锁定的表。
These systems lock files so that only one developer has write access to the central repository at a time.
这些系统对文件进行加锁，这样在某个时间只有一个开发人员对中心仓库具有写入权限。
On the surface it looks as though lock elision allows us to write thread safe code without any synchronization penalty for using in cases where it really wasn't needed.
从表面上看，锁省略似乎可以允许我们不必忍受同步带来的负担，就可以编写线程安全的代码了，前提是在同步的确是多余的情况下。
Once an exclusive lock has been issued, no other read or write operations can take place.
在发出独占锁定后，其他的读或写操作将不会再发生。
The s lock allows concurrent applications that use read-only queries to access the target table, but applications attempting to write data to the table are prevented from doing so.
s锁允许使用只读查询的并发应用程序访问目标表，但是防止应用程序写数据到表中。
For each bucket, there's a lock, and that lock is acquired when traversing a bucket either for read or write.
每个bucket都有一个锁，而且该锁在遍历bucket(为了读或写)的时候被获取。
To format the data about the deadlock event that the lock event monitor collects and write it to a plain text file, call the db2evmonfmt utility again.
为了格式化锁事件监控器收集的死锁事件数据，并将其写到普通文本文件中，再次调用db 2evmonfmt工具。
This is due to the way in which JFS2 is implemented with a write-exclusive inode lock, allowing multiples users to read the same file simultaneously.
这是因为JFS2在实现时使用了写独占(write - exclusive)索引节点锁，允许多个用户同时读取相同的文件。
LOCK_EX an exclusive lock. This denies all other processes both read and write access to the file.
排他锁。除加锁进程外其他进程没有对已加锁文件读写访问权限。
For example, if a thread enters a lock in upgradeable mode and then enters the lock in write mode, the order in which the thread exits the two modes does not matter.
例如，如果一个线程先进入可升级模式锁定状态，然后再进入写入模式锁定状态，则线程可以任何顺序退出这两种模式。
The system of this thesis employs scope consistency model, multi-write and lock-based cache protocol. In communication module, we propose a new framework.
数据同步方面系统采用了域一致性模型、多写协议，和基于锁的同步方式；
The current thread has entered read mode, so trying to enter the lock in write mode would create the possibility of a deadlock.
目前执行绪已进入读取模式，因此尝试进入写入模式锁定可能会造成死结。
The distributed lock system is used to synchronize GOS steps when accessing data. The consistency of the distributed cache is guaranteed by updating strategies of write-through and write-invalidate.
分布式锁管理机制实现了GOS之间数据访问的同步协调，写通和写—无效的数据更新策略保证了GOS的缓存一致性。
The distributed lock system is used to synchronize GOS steps when accessing data. The consistency of the distributed cache is guaranteed by updating strategies of write-through and write-invalidate.
分布式锁管理机制实现了GOS之间数据访问的同步协调，写通和写—无效的数据更新策略保证了GOS的缓存一致性。
应用推荐