From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id D40E8C6FA82 for ; Wed, 14 Sep 2022 14:24:04 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230084AbiINOYC (ORCPT ); Wed, 14 Sep 2022 10:24:02 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:36162 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230031AbiINOXU (ORCPT ); Wed, 14 Sep 2022 10:23:20 -0400 Received: from mail-pf1-x434.google.com (mail-pf1-x434.google.com [IPv6:2607:f8b0:4864:20::434]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 5D5E74F389 for ; Wed, 14 Sep 2022 07:23:18 -0700 (PDT) Received: by mail-pf1-x434.google.com with SMTP id y136so15096450pfb.3 for ; Wed, 14 Sep 2022 07:23:18 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fastly.com; s=google; h=user-agent:in-reply-to:content-disposition:mime-version:references :message-id:subject:cc:to:from:date:from:to:cc:subject:date; bh=7X3jI/FDmkrBs7DhtU4sYpQT4M91OAzd4bF9ysc8YQA=; b=kuTFYHmJmpQFxv2JP6mXl4t7RMOKICwKvTcwLslqUJQ/xIlbxwQYeNKTsYUk2K2fIw 16zOvbCrZ98E0IA/KYx5UktK/z6ClyAYPoHMSE7uJ30cU5o9IDFy857orY0dbk+oVpLL f/C15UDXNwotak1w8D3iBgvVTrcdx0jaXtqGY= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=user-agent:in-reply-to:content-disposition:mime-version:references :message-id:subject:cc:to:from:date:x-gm-message-state:from:to:cc :subject:date; bh=7X3jI/FDmkrBs7DhtU4sYpQT4M91OAzd4bF9ysc8YQA=; b=hH7dV8UqaXMFQDpO4y6wGjQgkvOVhPUBxHtclKd45w3u29ZBrhnYm0c2+HgKyIOXgX ccg7O5KVE2hRcEXPsZoITweYVAQKGAJndEu1/IaeqKowZZzubjrkkZMubYO7gO+A7ru0 wRN2N1hZ3tfZrTda1iTQj5HaPF3hbNHXfwXeuCBKjTDTQ3bVju0jf3oq1h8eL+ahbQTO nuEJ0pKddwFgoF0/oMGZG+s2y8x4HlnAOkTxkLKFvX0HQ3KgMKTMCUlGBJJIHbgWkWEW Bj868SOWxQb50nCVjwC4f4xxWultgJGcLGxBZWj5bs+X8Ou4u5DMTk+s0Ry+Tq2JYoKa 2pGQ== X-Gm-Message-State: ACgBeo1DrkGq1pdvPgtfwgLjcmk4WnWn/c5zgmVSlCrRSM02RnjGA9Vv VsXEP4tnhPr51qmuXQ0cIYt+Lg== X-Google-Smtp-Source: AA6agR5e0Wb81DIfJkmSV8Voh4NfgntHAxCLTOZXQzJ2lzogbO8SlJVIATVlUY6WISHAYjiZnqvEAw== X-Received: by 2002:a63:ed18:0:b0:439:4176:3ea6 with SMTP id d24-20020a63ed18000000b0043941763ea6mr7224872pgi.363.1663165397855; Wed, 14 Sep 2022 07:23:17 -0700 (PDT) Received: from fastly.com (c-73-223-190-181.hsd1.ca.comcast.net. [73.223.190.181]) by smtp.gmail.com with ESMTPSA id q6-20020aa78426000000b0053b9e5d365bsm5350864pfn.216.2022.09.14.07.23.15 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 14 Sep 2022 07:23:17 -0700 (PDT) Date: Wed, 14 Sep 2022 07:23:14 -0700 From: Joe Damato To: Peter Zijlstra Cc: Dave Hansen , x86@kernel.org, linux-mm@kvack.org, Dave Hansen , Andy Lutomirski , Thomas Gleixner , Ingo Molnar , Borislav Petkov , "H. Peter Anvin" , Juri Lelli , Vincent Guittot , Dietmar Eggemann , Steven Rostedt , Ben Segall , Mel Gorman , Daniel Bristot de Oliveira , Valentin Schneider , linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org Subject: Re: [RFC 1/1] mm: Add per-task struct tlb counters Message-ID: <20220914142313.GB4422@fastly.com> References: <1663120270-2673-1-git-send-email-jdamato@fastly.com> <1663120270-2673-2-git-send-email-jdamato@fastly.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.24 (2015-08-30) Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Sep 14, 2022 at 01:58:27PM +0200, Peter Zijlstra wrote: > On Wed, Sep 14, 2022 at 12:40:55AM -0700, Dave Hansen wrote: > > Why didn't the tracepoints work for you? > > This; perf should be able to get you per-task slices of those events. Thanks for taking a look; I replied to Dave with a longer form response, but IMHO, tracepoints are helpful in specific circumstances. On a heavily loaded system with O(10,000) or O(100,000) tasks, tracepoints can be difficult to use... especially if the TLB shootdown events are anomalous events that happen in large bursts at unknown intervals and are difficult to reproduce. IMHO, I think that being able to periodically scrape /proc to see that a particular process has a large TLB shootdown storm can then instruct you as to when to apply perf (and to which specific tasks) in order to debug the issue.