Received: by 2002:a25:31c3:0:0:0:0:0 with SMTP id x186csp1260207ybx; Thu, 7 Nov 2019 09:28:56 -0800 (PST) X-Google-Smtp-Source: APXvYqx+ymqUlwwjWz3yRSV3csCxNcKRV6mVrSLUrIKiEZ/EkGEhNX0J6kDIz1C+RsSpsuGvD3o/ X-Received: by 2002:aa7:d3da:: with SMTP id o26mr4982335edr.302.1573147736202; Thu, 07 Nov 2019 09:28:56 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1573147736; cv=none; d=google.com; s=arc-20160816; b=S6jZsOUOjwco0HTUPku5oyYBjRgqqv1f8nK56X6fbYIIHJo5fu19AVbctOyDwf45EE lkgKdTSKtIe7aQlxwVTLH3Ai9kjZum6/vjOpjNzeoGYVm+4gMFnWfGkGje+vfYSDiNd4 95kFCFa212r98oF0tWdP3GO0sR3VXBLhxGB77rul3+ilAIbfEWgaeJXI4gPhP4tegfr9 aSIL5pfJkgwXq4jrj4T3FO+gnLJDhQblBRaV4OLp7BgJhpc6+NkBabrGuqZdaKgrlzvj 9H+J2xlcHkWnfKmLb7b/7+Q5cdUmOWlttYlM4bECihX9de/J1ai0UK8NkpMJIbS1WMQm RWWQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:in-reply-to:content-disposition :mime-version:references:message-id:subject:cc:to:from:date; bh=uyWnJTiXk6j7YsxjBf/IAT0JhVzkn8tyYKltkvkeMkk=; b=n5MKXssOyblJ2tO2IWbuTj7+/0ZOWMkms9lRu9d/ENUQZ90FWKepBzpC45hNhG5l+h MWPEpQtAMPkn0n57eIolS6mIyFk9nX9DGU51D6A5uTjhbQ58q9N19EkzrbxZy3Rsa868 LQdzL0nN0A1M3e4VSrQATidE07IUba54IvaMgs0jFTH+QaE9cGGJRFV8VhXoAEL6Faop 43zSPK/3bH5yRKcu9HDrTR9ykLN16/th3aoDHzCrqTqAyOIcQRupmY+kQfk10bsbIzMG TuUG6GkwPRKt/8A/onPv3BvM4Ld+NoiIlcCrMRPW0fkVeNCZpeQZevVAnvX6vteYTfjk vNkg== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id c2si2191680eda.322.2019.11.07.09.28.32; Thu, 07 Nov 2019 09:28:56 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2389425AbfKGRYg (ORCPT + 99 others); Thu, 7 Nov 2019 12:24:36 -0500 Received: from Galois.linutronix.de ([193.142.43.55]:48846 "EHLO Galois.linutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1729669AbfKGRYg (ORCPT ); Thu, 7 Nov 2019 12:24:36 -0500 Received: from bigeasy by Galois.linutronix.de with local (Exim 4.80) (envelope-from ) id 1iSlWM-0002KO-3t; Thu, 07 Nov 2019 18:24:34 +0100 Date: Thu, 7 Nov 2019 18:24:34 +0100 From: Sebastian Andrzej Siewior To: Dennis Zhou Cc: linux-kernel@vger.kernel.org, Tejun Heo , Christoph Lameter , Thomas Gleixner , Peter Zijlstra , "Paul E. McKenney" Subject: Re: [PATCH] percpu-refcount: Use normal instead of RCU-sched" Message-ID: <20191107172434.ylz4hyxw4rbmhre2@linutronix.de> References: <20191002112252.ro7wpdylqlrsbamc@linutronix.de> <20191107091319.6zf5tmdi54amtann@linutronix.de> <20191107161749.GA93945@dennisz-mbp> <20191107162842.2qgd3db2cjmmsxeh@linutronix.de> <20191107165519.GA99408@dennisz-mbp> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <20191107165519.GA99408@dennisz-mbp> Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 2019-11-07 11:55:19 [-0500], Dennis Zhou wrote: > On Thu, Nov 07, 2019 at 05:28:42PM +0100, Sebastian Andrzej Siewior wrote: > > > I just want to clarify a little bit. Is this patch aimed at fixing an > > > issue with RT kernels specifically? > > > > Due to the implications of preempt_disable() on RT kernels it fixes > > problems with RT kernels. > > > > Great, do you mind adding this explanation with what the implications > are in the commit message? some RCU section here invoke callbacks which acquire spinlock_t locks. This does not work on RT with disabled preemption. > > > It'd also be nice to have the > > > numbers as well as if the kernel was RT or non-RT. > > > > The benchmark was done on a CONFIG_PREEMPT kernel. As said in the commit > > log, the numbers were mostly the same, I can re-run the test and post > > numbers if you want them. > > This patch makes no difference on PREEMPT_NONE or PREEMPT_VOLUNTARY > > kernels. > > > > I think a more explicit explanation in the commit message would suffice. What do you mean by "more explicit explanation"? The part with the numbers or that it makes no difference for PREEMPT_NONE and PREEMPT_VOLUNTARY? > Thanks, > Dennis Sebastian