Received: by 2002:a25:683:0:0:0:0:0 with SMTP id 125csp123313ybg; Tue, 2 Jun 2020 18:30:45 -0700 (PDT) X-Google-Smtp-Source: ABdhPJwYj46Vwcbm+v52svh+AFX45Jqw6lL9UaZkojRXSpEOALZUJ/nmB3uDtRBqaZDmKbakIz++ X-Received: by 2002:a17:907:7206:: with SMTP id dr6mr21645262ejc.335.1591147845594; Tue, 02 Jun 2020 18:30:45 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1591147845; cv=none; d=google.com; s=arc-20160816; b=YInfWtNjdkrOYTeJ2XsYfIxsFQA9UmRVg562iFAbgWNXllBPIdYuQQCzl9lMDbY15q U1q1b550aG/gzYyGYcqbXArWr3qcA6aqJVxdpH/9HLiLKmHLv1RJTl6HzVqIz3q1YzIY pS63ofvMkISiOyPnGi8/K/Kjk2JacuuiyXqN8KWtCcyquj52QA+m+lAdwHOD4MKEoE9m mfEgC3aYjkwM2vIL87JEOvV4Tcin26QQPy1Hm+BeCvgLCiBKFp1L3T/goaucXrTlgOBG qsYg9Q/MqwZtd4v+AEGpBv6yZ9jLuK3GDmqZ4RbHtb5WE3cH6g3irlHAUAHDebKT+ba+ GLxQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding :content-language:in-reply-to:mime-version:user-agent:date :message-id:from:references:cc:to:subject; bh=MGKqZLjT9DQfneDOl2jiw6IGmbGlxnc3rBspRDBnTjs=; b=cHQO3UHzGkWF4Wiav9R1SLr7zAU2oDxlxJ3CJhsE1vIQRelpj75dw1tAJ2XEom1P+L 0nD07oHO9kfiyQDaE1q8zoBNRQfgyJ0TIzCtU06NUYg+czD+VFnYNLee7p6K5zS+D7Cp FppJfRr4RjvLip/qRTH9Yz91nfrTsyk2dhWX12mEnG/uDJcSYrGWrLWdXZjZ/tqeiVww M7a0aFncCsTp6Em8H6zTYqjm15RWnpx1DAQVRVWTjHAtMd44S5o/27ROJwtiYp19q8Dl HNM/SBGLkpHeuIIi+szQi8fCiUZd1fyi/0C9cCrC3IXy/WirSCwoN1nV6HGeP8JuzGGh a+WA== 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 z15si223476eda.482.2020.06.02.18.30.16; Tue, 02 Jun 2020 18:30:45 -0700 (PDT) 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 S1727946AbgFCB2C (ORCPT + 99 others); Tue, 2 Jun 2020 21:28:02 -0400 Received: from foss.arm.com ([217.140.110.172]:56168 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726112AbgFCB2C (ORCPT ); Tue, 2 Jun 2020 21:28:02 -0400 Received: from usa-sjc-imap-foss1.foss.arm.com (unknown [10.121.207.14]) by usa-sjc-mx-foss1.foss.arm.com (Postfix) with ESMTP id 5F88255D; Tue, 2 Jun 2020 18:28:01 -0700 (PDT) Received: from [192.168.0.129] (unknown [172.31.20.19]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id 1DF4E3F6CF; Tue, 2 Jun 2020 18:27:57 -0700 (PDT) Subject: Re: [PATCH] mm/vmstat: Add events for PMD based THP migration without split To: Matthew Wilcox Cc: linux-mm@kvack.org, hughd@google.com, Naoya Horiguchi , Zi Yan , John Hubbard , Andrew Morton , linux-kernel@vger.kernel.org References: <1590118444-21601-1-git-send-email-anshuman.khandual@arm.com> <20200602150141.GN19604@bombadil.infradead.org> From: Anshuman Khandual Message-ID: <2d4634ce-9167-6ca6-fb91-f3c671fff672@arm.com> Date: Wed, 3 Jun 2020 06:56:57 +0530 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1 MIME-Version: 1.0 In-Reply-To: <20200602150141.GN19604@bombadil.infradead.org> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 06/02/2020 08:31 PM, Matthew Wilcox wrote: > On Fri, May 22, 2020 at 09:04:04AM +0530, Anshuman Khandual wrote: >> This adds the following two new VM events which will help in validating PMD >> based THP migration without split. Statistics reported through these events >> will help in performance debugging. >> >> 1. THP_PMD_MIGRATION_SUCCESS >> 2. THP_PMD_MIGRATION_FAILURE > > There's nothing actually PMD specific about these events, is there? > If we have a THP of a non-PMD size, you'd want that reported through the > same statistic, wouldn't you? Yes, there is nothing PMD specific here and we would use the same statistics for non-PMD size THP migration (if any) as well. But is THP migration really supported for non-PMD sizes ? CONFIG_ARCH_ENABLE_THP_MIGRATION depends upon CONFIG_TRANSPARENT_HUGEPAGE without being specific or denying about possible PUD level support. Fair enough, will drop the PMD from the events and their functions.