Received: by 2002:a25:ad19:0:0:0:0:0 with SMTP id y25csp496134ybi; Thu, 11 Jul 2019 23:34:20 -0700 (PDT) X-Google-Smtp-Source: APXvYqx1KA9UJ5EVvUT4hk3OlxyNoT5qOH0otmX9iaCT57estwoJwTxhRQivPsNDUIoSP8ST0K8r X-Received: by 2002:a17:90a:270f:: with SMTP id o15mr9714627pje.56.1562913260398; Thu, 11 Jul 2019 23:34:20 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1562913260; cv=none; d=google.com; s=arc-20160816; b=nKXh5ZlotukSBU2V0cqPpZr9CG46ZABlgkCtDyfpS+lfkTVNKFqfujzxeM3nqPy+eZ tPOK1BXC/uCtGytj3mCpBV7sr5JQR4jy5zmPZNctnwpfWxCI1jP3dOHWiseUyppeehs6 TKn3LgV6jhVVxOn9hCyhLnUMrOcnQH3kQMdaxesWTf6QTsslIfgelSjLiPC0Ca2/ryGc fpKytO07fC4VZUb9XO1/ojOMfRI4Yb4nufj8wvMhyZJjcV2iC13eI8cPPNLLuMO/iet8 T43v5sTdPbLRxqag+f9UtK2GS2S88kNXyUp9is2CIGBFa9jv5/ZsF6Bg+8KkCSPt7Xzl utxg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date; bh=DKrug69aZ3Di8F8614FZE+SiR9jTWIOKFs7Y6YDcArw=; b=Aiy9LsggGM6ZocaHhtllZsOuQEQLscUOkbiuAYYN8tT5pQDfKX4GaOMabkuyxWQNPr s0os//ClkJUxruxMa0nSqeIGJ7ndlYQIP/yJmprtUymexRSldlhChl1ETGGHSrQoQvM3 GeB39KPMvf1fB5DTjKaJZE7HZ4fNrV5n66ZvIVqibwECAn59w9a/fKznqF9il/bC3Qrf SoracR4ceQgy5xxgYcVgfU92dy2jyCOWw5qtu9H0afA5YNsG36c9X07kr7rhGBJdQTK1 /o+iMOXfatuQ2tZTyeduk+9UAS7FgW+TSVgEydG+IunjIg6cNh+Czo/6ljHgwx58KNXE UwDg== 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 f7si7244370pgr.536.2019.07.11.23.34.04; Thu, 11 Jul 2019 23:34:20 -0700 (PDT) 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 S1725987AbfGLGdj (ORCPT + 99 others); Fri, 12 Jul 2019 02:33:39 -0400 Received: from lgeamrelo13.lge.com ([156.147.23.53]:34777 "EHLO lgeamrelo11.lge.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1725562AbfGLGdj (ORCPT ); Fri, 12 Jul 2019 02:33:39 -0400 Received: from unknown (HELO lgeamrelo02.lge.com) (156.147.1.126) by 156.147.23.53 with ESMTP; 12 Jul 2019 15:33:36 +0900 X-Original-SENDERIP: 156.147.1.126 X-Original-MAILFROM: byungchul.park@lge.com Received: from unknown (HELO X58A-UD3R) (10.177.222.33) by 156.147.1.126 with ESMTP; 12 Jul 2019 15:33:36 +0900 X-Original-SENDERIP: 10.177.222.33 X-Original-MAILFROM: byungchul.park@lge.com Date: Fri, 12 Jul 2019 15:32:40 +0900 From: Byungchul Park To: Joel Fernandes Cc: "Paul E. McKenney" , josh@joshtriplett.org, rostedt@goodmis.org, mathieu.desnoyers@efficios.com, jiangshanlai@gmail.com, rcu@vger.kernel.org, linux-kernel@vger.kernel.org, kernel-team@lge.com Subject: Re: [PATCH] rcu: Make jiffies_till_sched_qs writable Message-ID: <20190712063240.GD7702@X58A-UD3R> References: <20190708125013.GG26519@linux.ibm.com> <20190708130359.GA42888@google.com> <20190709055815.GA19459@X58A-UD3R> <20190709124102.GR26519@linux.ibm.com> <20190710012025.GA20711@X58A-UD3R> <20190711123052.GI26519@linux.ibm.com> <20190711130849.GA212044@google.com> <20190711150215.GK26519@linux.ibm.com> <20190711164818.GA260447@google.com> <20190711195839.GA163275@google.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20190711195839.GA163275@google.com> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Jul 11, 2019 at 03:58:39PM -0400, Joel Fernandes wrote: > Hmm, speaking of grace period durations, it seems to me the maximum grace > period ever is recorded in rcu_state.gp_max. However it is not read from > anywhere. > > Any idea why it was added but not used? > > I am interested in dumping this value just for fun, and seeing what I get. > > I wonder also it is useful to dump it in rcutorture/rcuperf to find any > issues, or even expose it in sys/proc fs to see what worst case grace periods > look like. Hi, commit ae91aa0adb14dc33114d566feca2f7cb7a96b8b7 rcu: Remove debugfs tracing removed all debugfs tracing, gp_max also included. And you sounds great. And even looks not that hard to add it like, :) diff --git a/kernel/rcu/tree.c b/kernel/rcu/tree.c index ad9dc86..86095ff 100644 --- a/kernel/rcu/tree.c +++ b/kernel/rcu/tree.c @@ -1658,8 +1658,10 @@ static void rcu_gp_cleanup(void) raw_spin_lock_irq_rcu_node(rnp); rcu_state.gp_end = jiffies; gp_duration = rcu_state.gp_end - rcu_state.gp_start; - if (gp_duration > rcu_state.gp_max) + if (gp_duration > rcu_state.gp_max) { rcu_state.gp_max = gp_duration; + trace_rcu_grace_period(something something); + } /* * We know the grace period is complete, but to everyone else Thanks, Byungchul