tree c1282b207d116fdb56acb3782e9e59e05c7214df
parent d36a7a0d5e8b5bff1671723d733eb61621b0cee4
author Davidlohr Bueso <dave@stgolabs.net> 1410496841 -0700
committer Paul E. McKenney <paulmck@linux.vnet.ibm.com> 1410900067 -0700

locktorture: Add infrastructure for torturing read locks

Most of it is based on what we already have for writers. This allows
readers to be very independent (and thus configurable), enabling
future module parameters to control things such as rw distribution.
Furthermore, readers have their own delaying function, allowing us
to test different rw critical region latencies, and stress locking
internals. Similarly, statistics, for now will only serve for the
number of lock acquisitions -- as opposed to writers, readers have
no failure detection.

In addition, introduce a new nreaders_stress module parameter. The
default number of readers will be the same number of writers threads.
Writer threads are interleaved with readers. Documentation is updated,
respectively.

Signed-off-by: Davidlohr Bueso <dbueso@suse.de>
Signed-off-by: Paul E. McKenney <paulmck@linux.vnet.ibm.com>