Received: by 2002:a25:683:0:0:0:0:0 with SMTP id 125csp549523ybg; Tue, 9 Jun 2020 07:09:39 -0700 (PDT) X-Google-Smtp-Source: ABdhPJz3zTHdL3oAG4Cy4iDZF/x2eriFXgQryJFPeZLRK4lDXd5dN/lXU5/tVqtB/+7Xq1kX7fLk X-Received: by 2002:aa7:c944:: with SMTP id h4mr26553050edt.383.1591711778986; Tue, 09 Jun 2020 07:09:38 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1591711778; cv=none; d=google.com; s=arc-20160816; b=KDlwgVj0mYiku5FlNKrVVv4LkdA0EOK+WCUSPB5agtlWltjQSbOjh4tynohS5d1KW5 A5CWdWM0U7bozmdzvoaJ/uO0bSTmfU97URwgbEN3cZoxIj15Co8QbVePSKHkiyzBHgkE 15l9xxPblFqhy6aQfmHY8MIs6gZ4IGQgnL0DIbGqI7ktSat326/8gdUu1HI9I9dqfLf7 lR972yphqIm794dY2W6Cq85dEGLYNXnAPCn9eB3hgd9OpX9fCuK51SRhE6FeCKHn9OfD m7TvRbFuCkBunIHp7x6M/zo922Fhf7No0FFZXFqoPL5Rw0sOmtslWseKkX1u2ocgaKpC b4ew== 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:organization:autocrypt:from:references:cc:to:subject :dkim-signature; bh=PDlzQQ5oKYRRaYWAL/HDT5cz+wykF9SEdeyaLVMApFA=; b=v53xi7WrzVXIiwz6JtDxqlnca8lh3VasnVktJF//8TBDNHJoUxALor3vT1RlDYbUZ+ P7Ee1qZaiWnTH7+JCa0MoARIgDUSEhDZtKrCjjDtYbRaCpDAs8lkft1YcrqctlqH9zAw /8NldnIUkRDAr9bqG48gBOevSlTGf9nZyKPs7u/mXxFRVIJflAgSKikvrqlydnBDS8jT X5mbNQ6itvt7Z6C1ZY5sbJIDmwqQ7E7DKizXuni+XUcmaJYcBDdHBDkIw/Cnt0JL3o2P RzCR0PmuXIdbmRUt9tgBYg1Krpb7YDhk1bg71WBV3OWnNxx0yXAcc+HUICAMX2nyzEtl 8dXA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=UsujlYtH; 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; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id l12si9861428eje.751.2020.06.09.07.09.15; Tue, 09 Jun 2020 07:09:38 -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; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=UsujlYtH; 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; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1730125AbgFIOH2 (ORCPT + 99 others); Tue, 9 Jun 2020 10:07:28 -0400 Received: from us-smtp-delivery-1.mimecast.com ([207.211.31.120]:57418 "EHLO us-smtp-1.mimecast.com" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1728829AbgFIOH1 (ORCPT ); Tue, 9 Jun 2020 10:07:27 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1591711645; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references:autocrypt:autocrypt; bh=PDlzQQ5oKYRRaYWAL/HDT5cz+wykF9SEdeyaLVMApFA=; b=UsujlYtH6kDYIUCl3G3ouHs1ZGc9W+7VW9wTqJDy0Mwqk7pnvY+vtLdyv6HcWQdTEC1uH2 BNf5HQyGnncyhnGqqn9mDpFb0F4pOqIPcJSoRUAjXDvg7s7VFlXnDq6fVtIV/uRKH58H9I NfNFiq4ckI9oEg3lUUxuPbVO7vDqTl4= Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-47-0ocdvd3tP_eQPi4z7Gd6dQ-1; Tue, 09 Jun 2020 10:07:22 -0400 X-MC-Unique: 0ocdvd3tP_eQPi4z7Gd6dQ-1 Received: from smtp.corp.redhat.com (int-mx07.intmail.prod.int.phx2.redhat.com [10.5.11.22]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id C386457096; Tue, 9 Jun 2020 14:07:13 +0000 (UTC) Received: from [10.36.114.103] (ovpn-114-103.ams2.redhat.com [10.36.114.103]) by smtp.corp.redhat.com (Postfix) with ESMTP id C140C10013C1; Tue, 9 Jun 2020 14:07:01 +0000 (UTC) Subject: Re: [RFC v11 3/8] mm/damon: Implement data access monitoring-based operation schemes To: SeongJae Park Cc: akpm@linux-foundation.org, SeongJae Park , Jonathan.Cameron@Huawei.com, aarcange@redhat.com, acme@kernel.org, alexander.shishkin@linux.intel.com, amit@kernel.org, benh@kernel.crashing.org, brendan.d.gregg@gmail.com, brendanhiggins@google.com, cai@lca.pw, colin.king@canonical.com, corbet@lwn.net, dwmw@amazon.com, foersleo@amazon.de, irogers@google.com, jolsa@redhat.com, kirill@shutemov.name, mark.rutland@arm.com, mgorman@suse.de, minchan@kernel.org, mingo@redhat.com, namhyung@kernel.org, peterz@infradead.org, rdunlap@infradead.org, riel@surriel.com, rientjes@google.com, rostedt@goodmis.org, sblbir@amazon.com, shakeelb@google.com, shuah@kernel.org, sj38.park@gmail.com, snu@amazon.de, vbabka@suse.cz, vdavydov.dev@gmail.com, yang.shi@linux.alibaba.com, ying.huang@intel.com, linux-damon@amazon.com, linux-mm@kvack.org, linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org References: <20200609091725.15859-1-sjpark@amazon.com> From: David Hildenbrand Autocrypt: addr=david@redhat.com; prefer-encrypt=mutual; keydata= mQINBFXLn5EBEAC+zYvAFJxCBY9Tr1xZgcESmxVNI/0ffzE/ZQOiHJl6mGkmA1R7/uUpiCjJ dBrn+lhhOYjjNefFQou6478faXE6o2AhmebqT4KiQoUQFV4R7y1KMEKoSyy8hQaK1umALTdL QZLQMzNE74ap+GDK0wnacPQFpcG1AE9RMq3aeErY5tujekBS32jfC/7AnH7I0v1v1TbbK3Gp XNeiN4QroO+5qaSr0ID2sz5jtBLRb15RMre27E1ImpaIv2Jw8NJgW0k/D1RyKCwaTsgRdwuK Kx/Y91XuSBdz0uOyU/S8kM1+ag0wvsGlpBVxRR/xw/E8M7TEwuCZQArqqTCmkG6HGcXFT0V9 PXFNNgV5jXMQRwU0O/ztJIQqsE5LsUomE//bLwzj9IVsaQpKDqW6TAPjcdBDPLHvriq7kGjt WhVhdl0qEYB8lkBEU7V2Yb+SYhmhpDrti9Fq1EsmhiHSkxJcGREoMK/63r9WLZYI3+4W2rAc UucZa4OT27U5ZISjNg3Ev0rxU5UH2/pT4wJCfxwocmqaRr6UYmrtZmND89X0KigoFD/XSeVv jwBRNjPAubK9/k5NoRrYqztM9W6sJqrH8+UWZ1Idd/DdmogJh0gNC0+N42Za9yBRURfIdKSb B3JfpUqcWwE7vUaYrHG1nw54pLUoPG6sAA7Mehl3nd4pZUALHwARAQABtCREYXZpZCBIaWxk ZW5icmFuZCA8ZGF2aWRAcmVkaGF0LmNvbT6JAlgEEwEIAEICGwMFCQlmAYAGCwkIBwMCBhUI AgkKCwQWAgMBAh4BAheAFiEEG9nKrXNcTDpGDfzKTd4Q9wD/g1oFAl3pImkCGQEACgkQTd4Q 9wD/g1o+VA//SFvIHUAvul05u6wKv/pIR6aICPdpF9EIgEU448g+7FfDgQwcEny1pbEzAmiw zAXIQ9H0NZh96lcq+yDLtONnXk/bEYWHHUA014A1wqcYNRY8RvY1+eVHb0uu0KYQoXkzvu+s Dncuguk470XPnscL27hs8PgOP6QjG4jt75K2LfZ0eAqTOUCZTJxA8A7E9+XTYuU0hs7QVrWJ jQdFxQbRMrYz7uP8KmTK9/Cnvqehgl4EzyRaZppshruKMeyheBgvgJd5On1wWq4ZUV5PFM4x II3QbD3EJfWbaJMR55jI9dMFa+vK7MFz3rhWOkEx/QR959lfdRSTXdxs8V3zDvChcmRVGN8U Vo93d1YNtWnA9w6oCW1dnDZ4kgQZZSBIjp6iHcA08apzh7DPi08jL7M9UQByeYGr8KuR4i6e RZI6xhlZerUScVzn35ONwOC91VdYiQgjemiVLq1WDDZ3B7DIzUZ4RQTOaIWdtXBWb8zWakt/ ztGhsx0e39Gvt3391O1PgcA7ilhvqrBPemJrlb9xSPPRbaNAW39P8ws/UJnzSJqnHMVxbRZC Am4add/SM+OCP0w3xYss1jy9T+XdZa0lhUvJfLy7tNcjVG/sxkBXOaSC24MFPuwnoC9WvCVQ ZBxouph3kqc4Dt5X1EeXVLeba+466P1fe1rC8MbcwDkoUo65Ag0EVcufkQEQAOfX3n0g0fZz Bgm/S2zF/kxQKCEKP8ID+Vz8sy2GpDvveBq4H2Y34XWsT1zLJdvqPI4af4ZSMxuerWjXbVWb T6d4odQIG0fKx4F8NccDqbgHeZRNajXeeJ3R7gAzvWvQNLz4piHrO/B4tf8svmRBL0ZB5P5A 2uhdwLU3NZuK22zpNn4is87BPWF8HhY0L5fafgDMOqnf4guJVJPYNPhUFzXUbPqOKOkL8ojk CXxkOFHAbjstSK5Ca3fKquY3rdX3DNo+EL7FvAiw1mUtS+5GeYE+RMnDCsVFm/C7kY8c2d0G NWkB9pJM5+mnIoFNxy7YBcldYATVeOHoY4LyaUWNnAvFYWp08dHWfZo9WCiJMuTfgtH9tc75 7QanMVdPt6fDK8UUXIBLQ2TWr/sQKE9xtFuEmoQGlE1l6bGaDnnMLcYu+Asp3kDT0w4zYGsx 5r6XQVRH4+5N6eHZiaeYtFOujp5n+pjBaQK7wUUjDilPQ5QMzIuCL4YjVoylWiBNknvQWBXS lQCWmavOT9sttGQXdPCC5ynI+1ymZC1ORZKANLnRAb0NH/UCzcsstw2TAkFnMEbo9Zu9w7Kv AxBQXWeXhJI9XQssfrf4Gusdqx8nPEpfOqCtbbwJMATbHyqLt7/oz/5deGuwxgb65pWIzufa N7eop7uh+6bezi+rugUI+w6DABEBAAGJAiUEGAECAA8FAlXLn5ECGwwFCQlmAYAACgkQTd4Q 9wD/g1qA6w/+M+ggFv+JdVsz5+ZIc6MSyGUozASX+bmIuPeIecc9UsFRatc91LuJCKMkD9Uv GOcWSeFpLrSGRQ1Z7EMzFVU//qVs6uzhsNk0RYMyS0B6oloW3FpyQ+zOVylFWQCzoyyf227y GW8HnXunJSC+4PtlL2AY4yZjAVAPLK2l6mhgClVXTQ/S7cBoTQKP+jvVJOoYkpnFxWE9pn4t H5QIFk7Ip8TKr5k3fXVWk4lnUi9MTF/5L/mWqdyIO1s7cjharQCstfWCzWrVeVctpVoDfJWp 4LwTuQ5yEM2KcPeElLg5fR7WB2zH97oI6/Ko2DlovmfQqXh9xWozQt0iGy5tWzh6I0JrlcxJ ileZWLccC4XKD1037Hy2FLAjzfoWgwBLA6ULu0exOOdIa58H4PsXtkFPrUF980EEibUp0zFz GotRVekFAceUaRvAj7dh76cToeZkfsjAvBVb4COXuhgX6N4pofgNkW2AtgYu1nUsPAo+NftU CxrhjHtLn4QEBpkbErnXQyMjHpIatlYGutVMS91XTQXYydCh5crMPs7hYVsvnmGHIaB9ZMfB njnuI31KBiLUks+paRkHQlFcgS2N3gkRBzH7xSZ+t7Re3jvXdXEzKBbQ+dC3lpJB0wPnyMcX FOTT3aZT7IgePkt5iC/BKBk3hqKteTnJFeVIT7EC+a6YUFg= Organization: Red Hat GmbH Message-ID: <1f2ce1c6-2a09-667d-2bee-40215b421989@redhat.com> Date: Tue, 9 Jun 2020 16:07:00 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.8.0 MIME-Version: 1.0 In-Reply-To: <20200609091725.15859-1-sjpark@amazon.com> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.84 on 10.5.11.22 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 09.06.20 11:17, SeongJae Park wrote: > On Tue, 9 Jun 2020 10:47:45 +0200 David Hildenbrand wrote: > >> On 09.06.20 08:53, SeongJae Park wrote: >>> From: SeongJae Park >>> >>> In many cases, users might use DAMON for simple data access aware >>> memory management optimizations such as applying an operation scheme to >>> a memory region of a specific size having a specific access frequency >>> for a specific time. For example, "page out a memory region larger than >>> 100 MiB but having a low access frequency more than 10 minutes", or "Use >>> THP for a memory region larger than 2 MiB having a high access frequency >>> for more than 2 seconds". >>> >>> To minimize users from spending their time for implementation of such >>> simple data access monitoring-based operation schemes, this commit makes >>> DAMON to handle such schemes directly. With this commit, users can >>> simply specify their desired schemes to DAMON. >> >> What would be the alternative? How would a solution where these policies >> are handled by user space (or inside an application?) look like? > > Most simple form of the altermative solution would be doing offline data access > pattern profiling using DAMON and modifying the application source code or > system configuration based on the profiling results. > > More automated alternative solution would be a daemon constructed with two > modules: > > - monitor: monitors the data access pattern of the workload via the DAMON > debugfs interface > - memory manager: based on the monitoring result, make appropriate memory > management changes via mlock(), madvise(), sysctl, etc. > > The daemon would be able to run inside the application process as a thread, or > outside as a standalone process. If the daemon could not run inside the > application process, the memory management changes it could make would be > further limited, though, as mlock() and madvise() would not be available. The > madvise_process(), which is already merged in the next tree, would be helpful > in this case. > >>> >>> Each of the schemes is composed with conditions for filtering of the >>> target memory regions and desired memory management action for the >>> target. Specifically, the format is:: >>> >>> >>> >>> The filtering conditions are size of memory region, number of accesses >>> to the region monitored by DAMON, and the age of the region. The age of >>> region is incremented periodically but reset when its addresses or >>> access frequency has significantly changed or the action of a scheme was >>> applied. For the action, current implementation supports only a few of >>> madvise() hints, ``MADV_WILLNEED``, ``MADV_COLD``, ``MADV_PAGEOUT``, >>> ``MADV_HUGEPAGE``, and ``MADV_NOHUGEPAGE``. >> >> I am missing some important information. Is this specified for *all* >> user space processes? Or how is this configured? What are examples? >> >> E.g., messing with ``MADV_HUGEPAGE`` vs. ``MADV_NOHUGEPAGE`` of random >> applications can change the behavior/break these applications. (e.g., if >> userfaultfd is getting used and the applciation explicitly sets >> MADV_NOHUGEPAGE). > > Only monitoring target processes will be applied. The monitoring target > processes can be specified by writing the process ids to 'pids' debugfs file or > constructing the 'struct damon_ctx' via the programming interface. > > I will refine the commit message to make the points clearer, in the next spin. Understood, so a process configures damon to only modify its mappings. thanks for clarifying! This makes exposing the do_madvise() look less dangerous. -- Thanks, David / dhildenb