While Listing 6 shows push_back using the read-write lock.
清单6 给出使用读写锁的 push_back 方法。
Locking occurs on two levels (see Listing 7) : The list has a read-write lock, while individual nodes contain a mutex.
在两个级别上执行锁定(见清单7)：链表有一个读写锁，各个节点包含一个互斥锁。
The reason this technique is called the "cheap read-write lock" is that you are using different synchronization mechanisms for reads and writes.
之所以将这种技术称之为 “开销较低的读-写锁” 是因为您使用了不同的同步机制进行读写操作。
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.
有了这一类型的锁，并发应用程序就可以读或写已锁定的表。
Once an exclusive lock has been issued, no other read or write operations can take place.
在发出独占锁定后，其他的读或写操作将不会再发生。
For each bucket, there's a lock, and that lock is acquired when traversing a bucket either for read or write.
每个bucket都有一个锁，而且该锁在遍历bucket(为了读或写)的时候被获取。
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)索引节点锁，允许多个用户同时读取相同的文件。
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锁允许使用只读查询的并发应用程序访问目标表，但是防止应用程序写数据到表中。
LOCK_EX an exclusive lock. This denies all other processes both read and write access to the file.
排他锁。除加锁进程外其他进程没有对已加锁文件读写访问权限。
For example, if you have six databases and one takes a write lock, the other five are still available for read and write.
例如，如果你有六个数据库，其中一个有写锁，其他的五个仍然可以进行读写。
The current thread has entered read mode, so trying to enter the lock in write mode would create the possibility of a deadlock.
目前执行绪已进入读取模式，因此尝试进入写入模式锁定可能会造成死结。
The current thread has entered read mode, so trying to enter the lock in write mode would create the possibility of a deadlock.
目前执行绪已进入读取模式，因此尝试进入写入模式锁定可能会造成死结。
应用推荐