On 11/08/2013 06:51 PM, Paul E. McKenney wrote:
On Fri, Nov 08, 2013 at 05:36:12PM -0500, Waiman Long wrote:
I have some incorrect assumptions about memory barrier. Anyway, this
issue will be gone once I use the MCS lock/unlock code.
Here is a presentation that has some diagrams that might help
On Fri, Nov 08, 2013 at 05:36:12PM -0500, Waiman Long wrote:
> On 11/08/2013 04:11 PM, Paul E. McKenney wrote:
> >On Mon, Nov 04, 2013 at 12:17:17PM -0500, Waiman Long wrote:
> >>Kernel JPM %Change from (1)
> >>-- ---
> >> 1148265 -
> >> 2
On 11/08/2013 04:11 PM, Paul E. McKenney wrote:
On Mon, Nov 04, 2013 at 12:17:17PM -0500, Waiman Long wrote:
Kernel JPM %Change from (1)
-- ---
1148265 -
2238715 +61%
3242048 +63%
4234881 +58%
The use of
On Mon, Nov 04, 2013 at 12:17:17PM -0500, Waiman Long wrote:
> This patch introduces a new read/write lock implementation that put
> waiting readers and writers into a queue instead of actively contending
> the lock like the current read/write lock implementation. This will
> improve performance in
4 matches
Mail list logo
