Received: by 2002:a25:683:0:0:0:0:0 with SMTP id 125csp1025214ybg; Mon, 1 Jun 2020 22:34:01 -0700 (PDT) X-Google-Smtp-Source: ABdhPJxaM1HsYOrLhLo5WUzkm1tZyJCjlfw1K0qrpn8rP2F4NTCZVEpPENGr1l7kN60wy4qKZNpK X-Received: by 2002:a05:6402:17af:: with SMTP id j15mr23986727edy.67.1591076040891; Mon, 01 Jun 2020 22:34:00 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1591076040; cv=none; d=google.com; s=arc-20160816; b=WVeLGcKlWcZLNq6EThtQ9gf43TAyNrrwWdYJzOMK+gsZQSFvRo97GdogXgfqC0rT8K S3yBHGAflVCUq48WxLwc6s8jIqeEekbseWt+LEOA8aDv4Iz5lsw2ORFhkMZ7nk1WiT0U JO1osPC9Mye23/TEf5nrmlXi4UipRhzfNTXLVGQKJuauXXYMj9uXw389VBl1RuYjGG4M W6q5TOgxCNbkpwywafHVM2aM28RDjU7K6o3GWU/zY6IHWQzYS7L86JGT+fcAcXZbPlhp Mh7GyXCMNZg7fZDxjVs2qW4/a9Kh+R5ZIxIU0U+yloz74Y0YPkXsWDLQ53NCvlVwEoAH FO3g== 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=L0XwdRwPlo+FNTivI4+n03uNG/zU/FtOIL3C1BoV5lE=; b=vEGlj4BEUZuDyDFSqIX1U6xakT/1JzMsQr3XpN5r14p4b6P2MPIg69tfR3ZHjEu43T SjRKAdBUnc1sw8lrFfuHSyL5mFJyRcweD+bhcaBsIvfYBAsy9nOc3ZqwV3KPjgWsqYt0 ePU2gYbjnFeEGn3DZX1KrvqyRYxrIvakhlk37OB3WNp7fV6U4Wl2Jev94RB4HkjeLkJg k4cditX51FhTX/ceOmrB5t20rEy9V5xkXo+8zzElitLiMF7co+rJVtD+DOr0MR1LggCj MW+jZPZoEaVJc2KW9dqAzl8iza2emx0uGgsaTNOR1qIxd/z/Nj3+uwZh12zPztG7A22p UQ/Q== 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 r25si967370edi.172.2020.06.01.22.33.37; Mon, 01 Jun 2020 22:34:00 -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 S1725937AbgFBFbp (ORCPT + 99 others); Tue, 2 Jun 2020 01:31:45 -0400 Received: from foss.arm.com ([217.140.110.172]:46398 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725298AbgFBFbp (ORCPT ); Tue, 2 Jun 2020 01:31:45 -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 A0E511FB; Mon, 1 Jun 2020 22:31:44 -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 1DDDA3F52E; Mon, 1 Jun 2020 22:31:41 -0700 (PDT) Subject: Re: [PATCH] mm/vmstat: Add events for PMD based THP migration without split To: John Hubbard , Daniel Jordan Cc: linux-mm@kvack.org, hughd@google.com, Naoya Horiguchi , Zi Yan , Andrew Morton , linux-kernel@vger.kernel.org References: <1590118444-21601-1-git-send-email-anshuman.khandual@arm.com> <20200601165736.qw5kwwknxltk7bv6@ca-dmjordan1.us.oracle.com> <0a936ec7-f44f-1d72-915f-f5758d25fd72@nvidia.com> <1e71d815-5359-3ebe-5d2b-5a3b54b63b51@arm.com> <274be3bf-2206-5e98-8114-1d91fac472c9@nvidia.com> From: Anshuman Khandual Message-ID: Date: Tue, 2 Jun 2020 11:00:37 +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: <274be3bf-2206-5e98-8114-1d91fac472c9@nvidia.com> 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 10:18 AM, John Hubbard wrote: > On 2020-06-01 21:20, Anshuman Khandual wrote: > ... >>> also important: maybe this patch should also be tracking other causes >>> of THP PMD migration failure, in order to get a truer accounting of the >>> situation. > > I hope one of the experts here can weigh in on that... > >> Is there any other failure reasons which are only specific to THP migration. >> Else, adding stats about generic migration failure reasons will just blur >> the overall understanding about THP migration successes and failure cases >> that results in splitting. >> > > Thinking about that: we do have PGMIGRATE_SUCCESS and PGMIGRATE_FAIL, so I > suppose comparing those numbers with the new THP_PMD_MIGRATION_SUCCESS and > THP_PMD_MIGRATION_FAILURE events should cover it. That is right. > > However, the fact that this is under discussion hints at the need for a > bit of documentation help. What do you think about adding some notes about > all of this to, say, Documentation/vm/page_migration.rst ? Sure but probably bit later. Because I am also planning to add couple of trace events for THP migration, hence will update the documentation part for both VM stat and trace events together.