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 565DBC7619A for ; Tue, 11 Apr 2023 03:44:09 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230107AbjDKDoI (ORCPT ); Mon, 10 Apr 2023 23:44:08 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:41128 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230121AbjDKDnj (ORCPT ); Mon, 10 Apr 2023 23:43:39 -0400 Received: from verein.lst.de (verein.lst.de [213.95.11.211]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 9CADB213D for ; Mon, 10 Apr 2023 20:42:11 -0700 (PDT) Received: by verein.lst.de (Postfix, from userid 2407) id 47E8868BEB; Tue, 11 Apr 2023 05:41:37 +0200 (CEST) Date: Tue, 11 Apr 2023 05:41:37 +0200 From: "hch@lst.de" To: "Michael Kelley (LINUX)" Cc: Petr =?utf-8?B?VGVzYcWZw61r?= , "hch@lst.de" , "m.szyprowski@samsung.com" , "robin.murphy@arm.com" , Dexuan Cui , Tianyu Lan , "iommu@lists.linux.dev" , "linux-kernel@vger.kernel.org" Subject: Re: [PATCH v3 1/1] swiotlb: Track and report io_tlb_used high water mark in debugfs Message-ID: <20230411034137.GB15679@lst.de> References: <1680324300-124563-1-git-send-email-mikelley@microsoft.com> <20230407125535.476350d4@meshulam.tesarici.cz> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.17 (2007-11-01) Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Apr 07, 2023 at 10:05:26PM +0000, Michael Kelley (LINUX) wrote: > > Yes, this works fine now, but why are total_used and used_hiwater > > global variables? If you make them fields in struct io_tlb_mem > > (possibly guarded with #ifdef CONFIG_DEBUG_FS), you can get rid of the > > check. Of course, in instances other than io_tlb_default_mem these > > fields would not be exported to userspace through debugfs, but if really > > needed, I can at least find them in a crash dump (or read them through > > /proc/kcore). > > > > Got it. > > Your previously comments mentioned making them fields in struct io_tlb_mem, > and I missed your point. :-( I got focused on fixing the accounting for > DEBUG_FS so it didn't include the non-default pools, and didn't pick up on the > idea of doing the accounting for the non-default pools even though the values > aren't exposed in /sys. I'll fix this in the next version. FYI, I agree that per-instance accounting is probably the better way, too.