Received: by 2002:a05:6a10:16a7:0:0:0:0 with SMTP id gp39csp364528pxb; Wed, 18 Nov 2020 06:34:28 -0800 (PST) X-Google-Smtp-Source: ABdhPJwUYBylLeEosXyq2wDI+9NUmm6L6xdiklaaLSpyQ3wVZUfjLcMQsdfB+KsKEG2pT2uls/Yb X-Received: by 2002:a17:907:4186:: with SMTP id mz6mr25172805ejb.175.1605710067766; Wed, 18 Nov 2020 06:34:27 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1605710067; cv=none; d=google.com; s=arc-20160816; b=CbZ7CYKFeZFjkEsCmIA5cTNkdRABTTkRqskwYT6/tHQdzcUTkcKuWzMLjkAQjX075s oyWJezSEjARwWZLhV29XeF5CGy1TStjTSb6NJxmKcc6BB1/GVJUOKStVo3gXWgjPGeOU tMMWLVlqGqc0377AzSjrf17kkUnOiIWWdQs8DRGjo4ocLpQsvSgmQOI6YyTZ6mCnQ6F5 j0H0UaGqJFcmLEdeyvu5SfYRrMwZq7NXwVSmKWT5FdlHWRsD7URW1GDEGc9nn4UbFC6s uERXjDulVjDWgVxqXgxAsclaJKm9xh6kTKEbAr7bgZRZB3mMxe6J3aaKKwmuybFhfd1/ 2o4w== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:content-language :in-reply-to:mime-version:user-agent:date:message-id:from:references :cc:to:subject; bh=DHRg2s0GD2tYkMF7Mcy3fw1VI2Zx4TBQC4M/l6kgiIc=; b=Cga8rBGr2kAHybCkKn3MsSE2NuuCVw9x3ojhKGbup7cjuQKCC4ST5/ZZx9KPrAzpKT gx2Lpzpg36J2JmS+Ynn1U8irU1Xewqz8W+DauMRPoD1NbRJ9TzaiuJZqaqjcHL5FHFPJ svakfqPH/TbZ3A+//3oUhIEC8+rKuQ/OElMvgvrm4zDx2LHDDNRT/eMH07ESyJshtdUM Nk3iwBvSfVTuZ2h+nrLFSY2lGuTGWTB6fIN5xhD++HUNEHHzCCakF6SRuKa7wDJHTr3B 2zE1m+tVf6O6KQajhDjn5fSDesNuO1YvA30+IsIo/MvdYC/qTRL+mj7SvihUOsnJ9hS+ LH3Q== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id m26si17386534edp.196.2020.11.18.06.34.03; Wed, 18 Nov 2020 06:34:27 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1725874AbgKROa1 (ORCPT + 99 others); Wed, 18 Nov 2020 09:30:27 -0500 Received: from www262.sakura.ne.jp ([202.181.97.72]:64328 "EHLO www262.sakura.ne.jp" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725613AbgKROa1 (ORCPT ); Wed, 18 Nov 2020 09:30:27 -0500 Received: from fsav104.sakura.ne.jp (fsav104.sakura.ne.jp [27.133.134.231]) by www262.sakura.ne.jp (8.15.2/8.15.2) with ESMTP id 0AIEU7re060626; Wed, 18 Nov 2020 23:30:07 +0900 (JST) (envelope-from penguin-kernel@i-love.sakura.ne.jp) Received: from www262.sakura.ne.jp (202.181.97.72) by fsav104.sakura.ne.jp (F-Secure/fsigk_smtp/550/fsav104.sakura.ne.jp); Wed, 18 Nov 2020 23:30:07 +0900 (JST) X-Virus-Status: clean(F-Secure/fsigk_smtp/550/fsav104.sakura.ne.jp) Received: from [192.168.1.9] (M106072142033.v4.enabler.ne.jp [106.72.142.33]) (authenticated bits=0) by www262.sakura.ne.jp (8.15.2/8.15.2) with ESMTPSA id 0AIEU7EL060617 (version=TLSv1.2 cipher=AES256-GCM-SHA384 bits=256 verify=NO); Wed, 18 Nov 2020 23:30:07 +0900 (JST) (envelope-from penguin-kernel@i-love.sakura.ne.jp) Subject: Re: [PATCH v3] lockdep: Allow tuning tracing capacity constants. To: Peter Zijlstra Cc: Ingo Molnar , Will Deacon , Andrew Morton , linux-kernel@vger.kernel.org, Dmitry Vyukov , Linus Torvalds References: <1595640639-9310-1-git-send-email-penguin-kernel@I-love.SAKURA.ne.jp> <384ce711-25c5-553b-8d22-965847132fbd@i-love.sakura.ne.jp> <0eb519fa-e77b-b655-724a-4e9eecc64626@i-love.sakura.ne.jp> <6933e938-f219-5e13-aee6-fe4de87eb43e@i-love.sakura.ne.jp> <81ab0ffd-6e80-c96c-053a-b1b4fe8694c1@i-love.sakura.ne.jp> <20201118142357.GW3121392@hirez.programming.kicks-ass.net> From: Tetsuo Handa Message-ID: <1778f2e5-0a0c-2c6e-2c83-fe51d938e8a2@i-love.sakura.ne.jp> Date: Wed, 18 Nov 2020 23:30:05 +0900 User-Agent: Mozilla/5.0 (Windows NT 6.3; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.4.3 MIME-Version: 1.0 In-Reply-To: <20201118142357.GW3121392@hirez.programming.kicks-ass.net> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org The problem is that we can't know what exactly is consuming these resources. My question is do you have a plan to make it possible to know what exactly is consuming these resources. On 2020/11/18 23:23, Peter Zijlstra wrote: > On Wed, Nov 18, 2020 at 10:57:08PM +0900, Tetsuo Handa wrote: >> Peter, do you have a plan to make this problem actionable? > > I don't even know what the problem is.. nor do you. You can keep sending > this bad paper-over-issues patch until you're blue in the face, I'll not > take it for reasons I've explained before. > > I've also previously said that the right way to go about this is to > figure out what exactly is consuming these resources and then figure out > how to cure _that_. Blindly increasing the number only enables bad > actors to get away with being bad. >