1. 14 Jan, 2017 1 commit
  2. 22 Sep, 2016 1 commit
  3. 28 Apr, 2016 1 commit
  4. 06 Oct, 2015 1 commit
    • Davidlohr Bueso's avatar
      locktorture: Support rtmutex torturing · 095777c4
      Davidlohr Bueso authored
      Real time mutexes is one of the few general primitives
      that we do not have in locktorture. Address this -- a few
      considerations:
      
      o To spice things up, enable competing thread(s) to become
      rt, such that we can stress different prio boosting paths
      in the rtmutex code. Introduce a ->task_boost callback,
      only used by rtmutex-torturer. Tasks will boost/deboost
      around every 50k (arbitrarily) lock/unlock operations.
      
      o Hold times are similar to what we have for other locks:
      only occasionally having longer hold times (per ~200k ops).
      So we roughly do two full rt boost+deboosting ops with
      short hold times.
      Signed-off-by: default avatarDavidlohr Bueso <dbueso@suse.de>
      Signed-off-by: default avatarPaul E. McKenney <paulmck@linux.vnet.ibm.com>
      Reviewed-by: default avatarJosh Triplett <josh@joshtriplett.org>
      095777c4
  5. 18 Sep, 2015 1 commit
  6. 13 Sep, 2015 1 commit
  7. 28 Jan, 2015 1 commit
  8. 16 Jan, 2015 1 commit
  9. 29 Dec, 2014 1 commit
    • Henrik Austad's avatar
      Update of Documentation/00-INDEX · 8ea8f3eb
      Henrik Austad authored
      Added files
      - hsi.txt was added by 3a8ab8af (HSI: Add some general description for
        the HSI subsystem)
      - lzo.txt was added by d98a0526 (lzo: document part of the encoding)
      - xillybus.txt was added by 7051924f (xillybus: Move out of staging)
      - mailbox.txt was added by 15320fbc (add documentation for mailbox
        framework)
      
      Moved files
      - xommit 214e0aed (Move locking related docs into Documentation/locking/):
        * lockdep-design.txt
        * lockstat.txt
        * mutex-design.txt
        * rt-mutex-design.txt
        * rt-mutex.txt
        * spinlocks.txt
        * ww-mutex-design.txt
      - kselftest.txt was moved by 3c415707 (kselftest: Move the docs to the
        Documentation dir)
      
      CC: Davidlohr Bueso <davidlohr@hp.com>
      CC: Willy Tarreau <w@1wt.eu>
      CC: Randy Dunlap <rdunlap@infradead.org>
      CC: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
      CC: Sebastian Reichel <sre@kernel.org>
      CC: Eli Billauer <eli.billauer@gmail.com>
      CC: Jonathan Corbet <corbet@lwn.net>
      CC: Jiri Kosina <trivial@kernel.org>
      CC: linux-doc@vger.kernel.org
      CC: linux-kernel@vger.kernel.org
      Cc: Tim Bird <tim.bird@sonymobile.com>
      Cc: Shuah Khan <shuahkh@osg.samsung.com>
      Signed-off-by: default avatarHenrik Austad <henrik@austad.us>
      Signed-off-by: default avatarJonathan Corbet <corbet@lwn.net>
      8ea8f3eb
  10. 08 Dec, 2014 1 commit
  11. 30 Sep, 2014 1 commit
  12. 16 Sep, 2014 4 commits
    • Davidlohr Bueso's avatar
      locktorture: Support rwsems · 4a3b427f
      Davidlohr Bueso authored
      We can easily do so with our new reader lock support. Just an arbitrary
      design default: readers have higher (5x) critical region latencies than
      writers: 50 ms and 10 ms, respectively.
      Signed-off-by: default avatarDavidlohr Bueso <dbueso@suse.de>
      Signed-off-by: default avatarPaul E. McKenney <paulmck@linux.vnet.ibm.com>
      4a3b427f
    • Davidlohr Bueso's avatar
      locktorture: Add infrastructure for torturing read locks · 4f6332c1
      Davidlohr Bueso authored
      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: default avatarDavidlohr Bueso <dbueso@suse.de>
      Signed-off-by: default avatarPaul E. McKenney <paulmck@linux.vnet.ibm.com>
      4f6332c1
    • Davidlohr Bueso's avatar
      locktorture: Support mutexes · 42ddc75d
      Davidlohr Bueso authored
      Add a "mutex_lock" torture test. The main difference with the already
      existing spinlock tests is that the latency of the critical region
      is much larger. We randomly delay for (arbitrarily) either 500 ms or,
      otherwise, 25 ms. While this can considerably reduce the amount of
      writes compared to non blocking locks, if run long enough it can have
      the same torturous effect. Furthermore it is more representative of
      mutex hold times and can stress better things like thrashing.
      Signed-off-by: default avatarDavidlohr Bueso <dbueso@suse.de>
      Signed-off-by: default avatarPaul E. McKenney <paulmck@linux.vnet.ibm.com>
      42ddc75d
    • Davidlohr Bueso's avatar
      locktorture: Add documentation · cdf26bb1
      Davidlohr Bueso authored
      Just like Documentation/RCU/torture.txt, begin a document for the
      locktorture module. This module is still pretty green, so I have
      just added some specific sections to the doc (general desc, params,
      usage, etc.). Further development should update the file.
      Signed-off-by: default avatarDavidlohr Bueso <dbueso@suse.de>
      [ paulmck: Apply Randy Dunlap review comments. ]
      Signed-off-by: default avatarPaul E. McKenney <paulmck@linux.vnet.ibm.com>
      cdf26bb1
  13. 13 Aug, 2014 2 commits