From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751352AbdBZS60 (ORCPT ); Sun, 26 Feb 2017 13:58:26 -0500 Received: from mx2.suse.de ([195.135.220.15]:34066 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751214AbdBZS6Z (ORCPT ); Sun, 26 Feb 2017 13:58:25 -0500 Date: Sun, 26 Feb 2017 10:58:16 -0800 From: Davidlohr Bueso To: Waiman Long Cc: Ingo Molnar , Peter Zijlstra , linux-kernel@vger.kernel.org Subject: Re: [PATCH-tip 3/3] locking/rwsem: Stop active read lock ASAP Message-ID: <20170226185816.GF5126@linux-80c1.suse> References: <1487786634-22641-1-git-send-email-longman@redhat.com> <1487786634-22641-4-git-send-email-longman@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline In-Reply-To: <1487786634-22641-4-git-send-email-longman@redhat.com> User-Agent: Mutt/1.5.24 (2015-08-30) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, 22 Feb 2017, Waiman Long wrote: >On a 2-socket 36-core 72-thread x86-64 E5-2699 v3 system, a rwsem >microbenchmark was run with 36 locking threads (one/core) doing 100k >reader and writer lock/unlock operations each, the resulting locking >rates (avg of 3 runs) on a 4.10 kernel were 561.4 Mop/s and 588.8 >Mop/s without and with the patch respectively. That was an increase >of about 5%. iirc this patch is a repost, no? If so, did you get a chance to measure single file access with direct io as dchinner suggested? Thanks, Davidlohr