Received: by 2002:a25:8b12:0:0:0:0:0 with SMTP id i18csp2531382ybl; Thu, 29 Aug 2019 09:23:14 -0700 (PDT) X-Google-Smtp-Source: APXvYqxYDsXDDeiEz1F+OE6gl5XN0+9RgVB6kjL5FJm0yJzEfw5c4HHKqkFRzC4yTzq/zNjkCJss X-Received: by 2002:a17:90a:9f4b:: with SMTP id q11mr10566685pjv.105.1567095794258; Thu, 29 Aug 2019 09:23:14 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1567095794; cv=none; d=google.com; s=arc-20160816; b=hXwNV7i1rebaCYsz/oeI0tyPdEqmBVC601Ju2MS00VX+HCgdjXh4zrhljJAIu2y/bg 8fWkjBlZVpYHSaqqITH3PCwoNgGKjpZU0pK8keW+7rOsd+qkCslNh79G5u5C5rZnzi7D EWs6oYRdPSbZ21+dlrUl6WmzXIAGy1Ih8dlXGWc5UM49ev80y4WxBjyxavmXCVSfx1N6 EzrKEQJtivLkIdRUwvJBBKYIFdfFHkVxxlVlxnVMx3ulyxfyqdb62pBRnRlKHSuJ+BWZ t2HPb6dxVE9id8FsJMCb4vVUQeB2e3lPF4SFv65yJv2gkPBU+PbYvD7SMQPhjcMlpmZW D5Mw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:dkim-signature; bh=PwdCLmEnBCgGjb7mKk7fVt700Y2LpOrkVz5yVS4vWNI=; b=NPZzjuXKlBto18R7FIrGpI4h1gT67/49hiYq9de2MU1MyhktRCJu4dLjMhX2CBh5d/ e09cKSPOMfdyleJnthfflwWLU0TD6kAEEU5usY8YJbsBd8WbxwJ519Wb7cExmV9hIXUE DO3ChUweGDFbVTQFoCmC9FFU5r+iKuzsrqZz9p4JgYCKAgj62xXORAnNBtGhhG6E/0nH HbC6ef2pWKzyhWQKJHPvivWaKeZDESmzKcoSUd28pV6lTroWGCWbuN52DO3VzOrNC8DO fqX4b+xhA6TRiP6rIceBKuiw6Zvc7WdzZACAkdPwLBuFMjWVvjtouqbHa2haRIdGVVgY /hLQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=WTVSQe3M; 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; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id v40si2604998pjb.7.2019.08.29.09.22.58; Thu, 29 Aug 2019 09:23:14 -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; dkim=pass header.i=@kernel.org header.s=default header.b=WTVSQe3M; 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; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727682AbfH2QWB (ORCPT + 99 others); Thu, 29 Aug 2019 12:22:01 -0400 Received: from mail.kernel.org ([198.145.29.99]:38920 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726973AbfH2QWA (ORCPT ); Thu, 29 Aug 2019 12:22:00 -0400 Received: from mail-wm1-f42.google.com (mail-wm1-f42.google.com [209.85.128.42]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id A5C2823427 for ; Thu, 29 Aug 2019 16:21:59 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1567095719; bh=yfzsmqtHVcxU58IiLWMkZ2wW2SOsZ+0cJNaEYROK0hg=; h=References:In-Reply-To:From:Date:Subject:To:Cc:From; b=WTVSQe3M3O36C2hHmO4C0PE5Jk4r6myJcarVYynfCz93uYgnG0Eg6NuyMvGs6f3jL n3laAbJx7/dxUnLKSSig2sxmXClBThloqMPAElS9lREgFtKrD6iBGFkpfuNNhEdaGu 6igLeVpsbJ8U5azWAejqfCEherJlWbm6kCaOtXmc= Received: by mail-wm1-f42.google.com with SMTP id d16so4466886wme.2 for ; Thu, 29 Aug 2019 09:21:59 -0700 (PDT) X-Gm-Message-State: APjAAAVJZDspOgjnmWpO33A+ZDV9Gk5/vIPs9Iv57IBWaopdROCIkHwB urRT9k4z0cHxb/hyPNmS48CLmQIeCDlEivDhTIlfXg== X-Received: by 2002:a1c:f910:: with SMTP id x16mr12055557wmh.173.1567095718086; Thu, 29 Aug 2019 09:21:58 -0700 (PDT) MIME-Version: 1.0 References: <20190828202330.GS26530@linux.ibm.com> <20190828210525.GB75931@google.com> <20190828211904.GX26530@linux.ibm.com> <20190828214241.GD75931@google.com> <20190828220108.GC26530@linux.ibm.com> <20190828221444.GA100789@google.com> <20190828231247.GE26530@linux.ibm.com> <20190829015155.GB100789@google.com> <20190829034336.GD4125@linux.ibm.com> <20190829144355.GE63638@google.com> <20190829160946.GP4125@linux.ibm.com> In-Reply-To: <20190829160946.GP4125@linux.ibm.com> From: Andy Lutomirski Date: Thu, 29 Aug 2019 09:21:46 -0700 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [RFC v1 2/2] rcu/tree: Remove dynticks_nmi_nesting counter To: paulmck@kernel.org Cc: Joel Fernandes , LKML , Frederic Weisbecker , Jonathan Corbet , Josh Triplett , Android Kernel Team , Lai Jiangshan , "open list:DOCUMENTATION" , Mathieu Desnoyers , Mauro Carvalho Chehab , rcu@vger.kernel.org, Steven Rostedt , Andrew Lutomirski Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Aug 29, 2019 at 9:10 AM Paul E. McKenney wrote: > > On Thu, Aug 29, 2019 at 10:43:55AM -0400, Joel Fernandes wrote: > > [ . . . ] > > > Paul, do we also nuke rcu_eqs_special_set()? Currently I don't see anyone > > using it. And also remove the bottom most bit of dynticks? > > > > Also what happens if a TLB flush broadcast is needed? Do we IPI nohz or idle > > CPUs are the moment? > > > > All of this was introduced in: > > b8c17e6664c4 ("rcu: Maintain special bits at bottom of ->dynticks counter") > > Adding Andy Lutomirski on CC. > > Andy, is this going to be used in the near term, or should we just get > rid of it? > Let's get rid of it. I'm not actually convinced it *can* be used as designed. For those who forgot the history or weren't cc'd on all of it: I had this clever idea about how we could reduce TLB flushes. I implemented some of it (but not the part that would have used this RCU feature), and it exploded in nasty and subtle ways. This caused me to learn that speculative TLB fills were a problem that I had entirely failed to account for. Then PTI happened and thoroughly muddied the water. So I think we should just drop this :(