Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756710AbbHZMTP (ORCPT ); Wed, 26 Aug 2015 08:19:15 -0400 Received: from mx1.redhat.com ([209.132.183.28]:37009 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751982AbbHZMTO (ORCPT ); Wed, 26 Aug 2015 08:19:14 -0400 Date: Wed, 26 Aug 2015 14:16:43 +0200 From: Oleg Nesterov To: "Paul E. McKenney" Cc: Ingo Molnar , Linus Torvalds , Peter Zijlstra , Tejun Heo , linux-kernel@vger.kernel.org Subject: Re: [PATCH v2 0/8] Add rcu_sync infrastructure to avoid _expedited() in percpu-rwsem Message-ID: <20150826121643.GA10831@redhat.com> References: <20150821174230.GA17867@redhat.com> <20150822163810.GV11078@linux.vnet.ibm.com> <20150824153431.GB24949@redhat.com> <20150826002220.GZ11078@linux.vnet.ibm.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20150826002220.GZ11078@linux.vnet.ibm.com> User-Agent: Mutt/1.5.18 (2008-05-17) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2028 Lines: 52 On 08/25, Paul E. McKenney wrote: > > On Mon, Aug 24, 2015 at 05:34:31PM +0200, Oleg Nesterov wrote: > > > > I booted the kernel with the additional patch below, and nothing bad has > > happened, it continues to print > > > > Writes: Total: 2 Max/Min: 0/0 Fail: 0 > > Reads : Total: 2 Max/Min: 0/0 Fail: 0 > > > > However, I do not know what this code actually does, so currently I have > > no idea if this test makes any sense for percpu_rw_semaphore. > > Actually, unless I am really confused, that does not look good... > > I would expect something like this, from a run with rwsem_lock: > > [ 16.336057] Writes: Total: 473 Max/Min: 0/0 Fail: 0 > [ 16.337615] Reads : Total: 219 Max/Min: 0/0 Fail: 0 > [ 31.338152] Writes: Total: 959 Max/Min: 0/0 Fail: 0 > [ 31.339114] Reads : Total: 437 Max/Min: 0/0 Fail: 0 > [ 46.340167] Writes: Total: 1365 Max/Min: 0/0 Fail: 0 > [ 46.341952] Reads : Total: 653 Max/Min: 0/0 Fail: 0 > [ 61.343027] Writes: Total: 1795 Max/Min: 0/0 Fail: 0 > [ 61.343968] Reads : Total: 865 Max/Min: 0/0 Fail: 0 > [ 76.344034] Writes: Total: 2220 Max/Min: 0/0 Fail: 0 > [ 76.345243] Reads : Total: 1071 Max/Min: 0/0 Fail: 0 > > The "Total" should increase for writes and for reads -- if you are > just seeing "Total: 2" over and over, that indicates that either > the torture test or rcu_sync got stuck somewhere. Hmm. I reverted the change in locktorture.c , and I see the same numbers when I boot the kernel with locktorture.verbose=1 locktorture.torture_type=rwsem_lock parameters. Writes: Total: 2 Max/Min: 0/0 Fail: 0 Reads : Total: 2 Max/Min: 0/0 Fail: 0 "Total" doesn't grow. Looks like something is wrong with locktorture. I'll try to re-check... Oleg. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/