Received: by 2002:a05:6a10:16a7:0:0:0:0 with SMTP id gp39csp597738pxb; Thu, 12 Nov 2020 11:16:25 -0800 (PST) X-Google-Smtp-Source: ABdhPJyCppi02IyBudhLhDU8Uqbs3UkxRzM/iyOvblIANI2u4iz0WsnnXINM3D7L3awTc6JU9+4o X-Received: by 2002:a05:6402:54d:: with SMTP id i13mr1479031edx.3.1605208584871; Thu, 12 Nov 2020 11:16:24 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1605208584; cv=none; d=google.com; s=arc-20160816; b=QZ9dxQVwbg+tsH7ZMGBk6X+72L25Dj7E3v5BPJu2b8aMb57FeRQM3FDjImwjHt2nFc v7BOIAwtJS4d5YJmCSqIlCkCBz+3ROG5X5GqBA2N31qLvRrgxe1eSY+KqwhRibr1jBL6 vxsP9HYLKuWlC9nTuogoGv3Eyp2zlCBBICAzmZLo7VIcy2+7eUwBnE2unFoQLGpEZmpq QojkQnYz22dchhSb6QhZEJzG9WvhuX+C8PS2nlwyndP/KK4QETVATTLQSjHvTSTI1npx LhsUMK9d3YvGVr9ifc3PRWlCaQ1ic/pVQFQREKKWnBFEiFdq+65TiUrYo/kD6pJHYoOw UMiA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :references:in-reply-to:message-id:subject:cc:to:from:date :dkim-signature; bh=APx5n9+R1UX7us9wtXaNCP3WPs18nVaJcTOhtANnj1w=; b=ICvU4jXKgu/XdQJ3tgssEQCNSfq5fUN9jw2V/AMVGtp0B7ntB+2aQLQ4ZhVJbi7Wem 6Wtk6l5ddZLIDRbiEtlbM8GKoCgtRft3jqUvTYxARSNEJieve3QvTRV2bXwbC83vRe/K tcoxZNqzNmpCo0pfgry0ZMpoOImRVA0B8Ulm5e0FamPfz5ufMNCQZImWl4ZOcqmhA6G+ +OCNDa3QOBROMJrOxQC9QlIC2fzc7wDIXqqDl4ThR6Vxmy1uL10W/pX3Ph09P1/2+mdK EqitupQNjxrhsOd46kSEPO337BJMgS79xICzTNfIJi+SKiwsLlyMS1Eq4MbrFVB8czU8 l1Jw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=Z26vT4aM; 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 hq23si4527328ejc.89.2020.11.12.11.15.59; Thu, 12 Nov 2020 11:16:24 -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; dkim=pass header.i=@kernel.org header.s=default header.b=Z26vT4aM; 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 S1726654AbgKLTOj (ORCPT + 99 others); Thu, 12 Nov 2020 14:14:39 -0500 Received: from mail.kernel.org ([198.145.29.99]:58914 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726255AbgKLTOj (ORCPT ); Thu, 12 Nov 2020 14:14:39 -0500 Received: from localhost.localdomain (c-73-231-172-41.hsd1.ca.comcast.net [73.231.172.41]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id C13DB20B80; Thu, 12 Nov 2020 19:14:36 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1605208477; bh=CQVrsFhxionALStdHqSmv142xPjtDpVoDmH7rt3JLrs=; h=Date:From:To:Cc:Subject:In-Reply-To:References:From; b=Z26vT4aMSGqAp0sVbnHuMR0uVxLCBTcSlxFb7/2U0jfyII9e4vT1jV/5prGT1ap7w 6VIn+2HY2sOE2Y4VNyK4dEqzXYavtN9rgMADFFBGHH05hJnMJHwXNDUPHWgZZxaT8p uT54M/AtWDXghvMBtV+mxfqdHeOGt0gh7vq1hc20= Date: Thu, 12 Nov 2020 11:14:36 -0800 From: Andrew Morton To: Georgi Djakov Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org, sudaraja@codeaurora.org, pratikp@codeaurora.org, lmark@codeaurora.org Subject: Re: [PATCH] mm/page_owner: Record timestamp and pid Message-Id: <20201112111436.c5deeadd3578877fc0b844a1@linux-foundation.org> In-Reply-To: <20201112184106.733-1-georgi.djakov@linaro.org> References: <20201112184106.733-1-georgi.djakov@linaro.org> X-Mailer: Sylpheed 3.5.1 (GTK+ 2.24.31; x86_64-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, 12 Nov 2020 20:41:06 +0200 Georgi Djakov wrote: > From: Liam Mark > > Collect the time for each allocation recorded in page owner so that > allocation "surges" can be measured. > > Record the pid for each allocation recorded in page owner so that > the source of allocation "surges" can be better identified. Please provide a description of why this is considered useful. What has it been used for, what problems has it been used to solve? Are there userspace tools which aid in the processing of this new information? Can/should Documentation/vm/page_owner.rst be updated? > --- a/mm/page_owner.c > +++ b/mm/page_owner.c > @@ -10,6 +10,7 @@ > #include > #include > #include > +#include > > #include "internal.h" > > @@ -25,6 +26,8 @@ struct page_owner { > gfp_t gfp_mask; > depot_stack_handle_t handle; > depot_stack_handle_t free_handle; > + u64 ts_nsec; > + int pid; pid_t would be nicer?