Re: [RFC PATCH-tip v2 2/6] locking/rwsem: Stop active read lock ASAP

From	Davidlohr Bueso <dave@stgolabs.net>
Newsgroups	linux.kernel
Subject	Re: [RFC PATCH-tip v2 2/6] locking/rwsem: Stop active read lock ASAP
Date	2016-06-16 04:20 +0200
Message-ID	<rKv4t-2mG-1@gated-at.bofh.it> (permalink)
References	<rK5jH-2zl-5@gated-at.bofh.it> <rK5to-2E2-31@gated-at.bofh.it> <rKmNz-5ul-17@gated-at.bofh.it> <rKv4u-2mG-3@gated-at.bofh.it>
Organization	linux.* mail to news gateway

Show all headers | View raw

On Wed, 15 Jun 2016, Waiman Long wrote:

>I think there will be a little bit of performance impact for a 
>workload that produce just the right amount of rwsem contentions. 

I'm not saying the change doesn't make sense, but this is the sort of
thing that will show nice numbers in one workload and go bite you in
another.

Thanks,
Davidlohr

Back to linux.kernel | Previous | Next — Previous in thread | Find similar | Unroll thread

Thread

[RFC PATCH-tip v2 0/6] locking/rwsem: Enable reader optimistic spinning Waiman Long <Waiman.Long@hpe.com> - 2016-06-15 00:50 +0200
  [RFC PATCH-tip v2 2/6] locking/rwsem: Stop active read lock ASAP Waiman Long <Waiman.Long@hpe.com> - 2016-06-15 01:00 +0200
    Re: [RFC PATCH-tip v2 2/6] locking/rwsem: Stop active read lock ASAP Peter Zijlstra <peterz@infradead.org> - 2016-06-15 19:30 +0200
      Re: [RFC PATCH-tip v2 2/6] locking/rwsem: Stop active read lock ASAP Davidlohr Bueso <dave@stgolabs.net> - 2016-06-16 04:20 +0200

csiph-web