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 mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id E7ECAC433FE for ; Sun, 10 Oct 2021 22:01:45 +0000 (UTC) Received: from kanga.kvack.org (kanga.kvack.org [205.233.56.17]) by mail.kernel.org (Postfix) with ESMTP id 65F3560EFE for ; Sun, 10 Oct 2021 22:01:45 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.4.1 mail.kernel.org 65F3560EFE Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=linux-foundation.org Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=kvack.org Received: by kanga.kvack.org (Postfix) id D57FF940008; Sun, 10 Oct 2021 18:01:44 -0400 (EDT) Received: by kanga.kvack.org (Postfix, from userid 40) id D0794940007; Sun, 10 Oct 2021 18:01:44 -0400 (EDT) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id BF5D3940008; Sun, 10 Oct 2021 18:01:44 -0400 (EDT) X-Delivered-To: linux-mm@kvack.org Received: from forelay.hostedemail.com (smtprelay0191.hostedemail.com [216.40.44.191]) by kanga.kvack.org (Postfix) with ESMTP id ADDE4940007 for ; Sun, 10 Oct 2021 18:01:44 -0400 (EDT) Received: from smtpin32.hostedemail.com (10.5.19.251.rfc1918.com [10.5.19.251]) by forelay02.hostedemail.com (Postfix) with ESMTP id 58BD92D247 for ; Sun, 10 Oct 2021 22:01:44 +0000 (UTC) X-FDA: 78681900528.32.4173BE6 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by imf16.hostedemail.com (Postfix) with ESMTP id 05C73F000AE7 for ; Sun, 10 Oct 2021 22:01:43 +0000 (UTC) Received: by mail.kernel.org (Postfix) with ESMTPSA id 8CC4D60ED7; Sun, 10 Oct 2021 22:01:42 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=linux-foundation.org; s=korg; t=1633903303; bh=lo9M+TDpC7LJs9JEpSPlR/TOsXRJVkyYrlp/12sLFj4=; h=Date:From:To:Cc:Subject:In-Reply-To:References:From; b=vXfG4FjMIJU43l453teCwBEi3xUtQWjwfj6iqPEyK41FtzBhpE5xvhAzquqZ/zHS0 4uKaGjqZHJKAQO29TwT5mVNjmFz2DBUAXzb+L8greEkwwmIvKRVANqWChrW4qr3/9u wi62lTjaqMWZSsMVhAYfDaaMidNjCS9rOS7YQXcc= Date: Sun, 10 Oct 2021 15:01:40 -0700 From: Andrew Morton To: SeongJae Park Cc: Jonathan.Cameron@Huawei.com, amit@kernel.org, benh@kernel.crashing.org, corbet@lwn.net, david@redhat.com, dwmw@amazon.com, elver@google.com, foersleo@amazon.de, gthelen@google.com, markubo@amazon.de, rientjes@google.com, shakeelb@google.com, shuah@kernel.org, linux-damon@amazon.com, linux-mm@kvack.org, linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH 1/4] mm/damon/dbgfs: Implement recording feature Message-Id: <20211010150140.be96f07048079188d9d6b613@linux-foundation.org> In-Reply-To: <20211008094509.16179-1-sj@kernel.org> References: <20211008094509.16179-1-sj@kernel.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 X-Rspamd-Server: rspam02 X-Rspamd-Queue-Id: 05C73F000AE7 X-Stat-Signature: q5ug1fcweof9k8f5bwhnmgfq8db1b83u Authentication-Results: imf16.hostedemail.com; dkim=pass header.d=linux-foundation.org header.s=korg header.b=vXfG4FjM; spf=pass (imf16.hostedemail.com: domain of akpm@linux-foundation.org designates 198.145.29.99 as permitted sender) smtp.mailfrom=akpm@linux-foundation.org; dmarc=none X-HE-Tag: 1633903303-225945 X-Bogosity: Ham, tests=bogofilter, spamicity=0.000000, version=1.2.4 Sender: owner-linux-mm@kvack.org Precedence: bulk X-Loop: owner-majordomo@kvack.org List-ID: On Fri, 8 Oct 2021 09:45:06 +0000 SeongJae Park wrote: > The user space can get the monitoring results via the 'damon_aggregated' > tracepoint event. For simplicity and brevity, the tracepoint events > have some duplicated information such as 'target_id' and 'nr_regions', > though. As a result, its size is greater than really needed. Also, > dealing with the tracepoint could be complex for some simple use cases. > To provide a way for getting more efficient and simple monitoring > results to user space, this commit implements 'recording' feature in > 'damon-dbgfs'. > > The feature is exported to the user space via a new debugfs file named > 'record', which is located in '/damon/' directory. The file > allows users to record monitored access patterns in a regular binary > file in a simple format. Binary files are troublesome. Is the format of this file documented anywhere? I assume that the file's contents will have different representations depending on host endianness and word size and I further assume that the provided python script won't handle this very well? > The recorded results are first written in an > in-memory buffer and flushed to a file in batch. Users can get and set > the size of the buffer and the path to the result file by reading from > and writing to the 'record' file. For example, below commands set the > buffer to be 4 KiB and the result to be saved in '/damon.data'. > With a simple test workload[1], recording the tracepoint event using > 'perf-record' results in 1.7 MiB 'perf.data' file. When the access > pattern is recorded via this feature, the size is reduced to 264 KiB. > Also, the resulting record file is simple enough to be manipulated by a > small (100 lines of code) python script which will be introduced by a > following commit ("selftests/damon: Test recording feature"). How useful and important is this? I mean, is it tremendously better or is it a little bit nice to have? A description of the overall benefit to DAMON users would be useful in helping others to understand the benefit of this change.