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 kanga.kvack.org (kanga.kvack.org [205.233.56.17]) by smtp.lore.kernel.org (Postfix) with ESMTP id 4F22FE6B278 for ; Fri, 1 Nov 2024 13:25:02 +0000 (UTC) Received: by kanga.kvack.org (Postfix) id A6FE46B0093; Fri, 1 Nov 2024 09:25:01 -0400 (EDT) Received: by kanga.kvack.org (Postfix, from userid 40) id A20ED6B0095; Fri, 1 Nov 2024 09:25:01 -0400 (EDT) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id 8E8916B0096; Fri, 1 Nov 2024 09:25:01 -0400 (EDT) X-Delivered-To: linux-mm@kvack.org Received: from relay.hostedemail.com (smtprelay0011.hostedemail.com [216.40.44.11]) by kanga.kvack.org (Postfix) with ESMTP id 6F8F16B0093 for ; Fri, 1 Nov 2024 09:25:01 -0400 (EDT) Received: from smtpin01.hostedemail.com (a10.router.float.18 [10.200.18.1]) by unirelay09.hostedemail.com (Postfix) with ESMTP id 1AC1B80496 for ; Fri, 1 Nov 2024 13:25:01 +0000 (UTC) X-FDA: 82737595374.01.11A035A Received: from frasgout.his.huawei.com (frasgout.his.huawei.com [185.176.79.56]) by imf22.hostedemail.com (Postfix) with ESMTP id BD8D5C001F for ; Fri, 1 Nov 2024 13:24:23 +0000 (UTC) Authentication-Results: imf22.hostedemail.com; dkim=none; dmarc=pass (policy=quarantine) header.from=huawei.com; spf=pass (imf22.hostedemail.com: domain of stepanov.anatoly@huawei.com designates 185.176.79.56 as permitted sender) smtp.mailfrom=stepanov.anatoly@huawei.com ARC-Seal: i=1; s=arc-20220608; d=hostedemail.com; t=1730467442; a=rsa-sha256; cv=none; b=0cBumt1piUaz+j8qJaITvWs+jcL5rGiG57M+BRi8FYicqFcUD9dITcbMqvZ5GdjvuttH4W SaF4PFYXTtZUEYbM8qFuTKl2XaH7ac/eu2B64M7Ln2+BnsQDQofSH2WhnOn4GFgitMC0d4 InEbNmRhUqCJTyJOODTQUTPUTH8UUUM= ARC-Authentication-Results: i=1; imf22.hostedemail.com; dkim=none; dmarc=pass (policy=quarantine) header.from=huawei.com; spf=pass (imf22.hostedemail.com: domain of stepanov.anatoly@huawei.com designates 185.176.79.56 as permitted sender) smtp.mailfrom=stepanov.anatoly@huawei.com ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=hostedemail.com; s=arc-20220608; t=1730467442; h=from:from:sender: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; bh=0t4WTPCpyLcux3OrkmzshxVG7pMlJq96VUif4OkaQKk=; b=OqMgTbZpypDwJguC77yv/kqj+HNgjf4aJ5odI4dRF8jHqlW9QIymg7hoOohAMiFdfjwhC/ OVCfrsexh1/KQdsOj5Cz6PM6rg3mEGKT0fGpG/cNFph1C5V2JvYN5UO/3JTgc8TDt18ZrS s+fv675/9X/vQRbIGfWZ/Q9sXBt4TEY= Received: from mail.maildlp.com (unknown [172.18.186.31]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4Xg1k86cLgz6K6N8; Fri, 1 Nov 2024 21:22:24 +0800 (CST) Received: from mscpeml500003.china.huawei.com (unknown [7.188.49.51]) by mail.maildlp.com (Postfix) with ESMTPS id 657E71400D3; Fri, 1 Nov 2024 21:24:56 +0800 (CST) Received: from [10.123.123.226] (10.123.123.226) by mscpeml500003.china.huawei.com (7.188.49.51) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.1258.34; Fri, 1 Nov 2024 16:24:55 +0300 Message-ID: <5120497d-d60a-4a4b-a39d-9b1dbe89154c@huawei.com> Date: Fri, 1 Nov 2024 16:24:55 +0300 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: [RFC PATCH 0/3] Cgroup-based THP control To: Michal Hocko CC: Gutierrez Asier , , , , , , , , , , , , , , , , , , , , , , , References: <770bf300-1dbb-42fc-8958-b9307486178e@huawei-partners.com> <80d76bad-41d8-4108-ad74-f891e5180e47@huawei.com> <274e1560-9f6c-4dd9-b27c-2fd0f0c54d03@huawei.com> Content-Language: en-US From: Stepanov Anatoly In-Reply-To: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Originating-IP: [10.123.123.226] X-ClientProxiedBy: mscpeml100003.china.huawei.com (10.199.174.67) To mscpeml500003.china.huawei.com (7.188.49.51) X-Rspam-User: X-Rspamd-Queue-Id: BD8D5C001F X-Rspamd-Server: rspam11 X-Stat-Signature: bh5359b7w896aftkaq3wg3yy5onkbr78 X-HE-Tag: 1730467463-153658 X-HE-Meta: U2FsdGVkX189mPRpo07coI8u5xwQcNx+el069uoJMJnMtkMo3OFRgSfvbBGA9Vz4NuDrMjvaEyYlKdQUsdOKapcvMeCxZnCdccOJyrq60Fo55lGN8HA/bHg9bpGIzCnq8YWPqZGPB+O18Te55nZVJtPSV7zpVjfr9BMyvKyQ+bdWFYn7NzAYpAdbNY09cseLi1p91LxLgFRgbNGOj1MXLxcmKU1o77ZHbpAd+HVYpV1UR3Amd06Nfk9A7uzwn3UyF757FsA/wn3HFc3E+fYw8KqH5sMDT4V7nQKUK8pBuhdvnhjP4llv/Aer9hLpSwckNw8VMcCAZ3TWeQQKkBzCz412M/tOdf/74HdtaFpPSGVOZY6MmnTuPiIEQg3T0nH/VLpIhaKn/724Pq2Z3lYt3Wmtjg1xVT8vIIa7mt95TXboiP39DheQJN4VO3uKGu8+MpXJ3bF0iWowNnyEhXdLJ65+Jl/kPGPHqxa2TxO2I8nPDy5gk2Uhz8YX8cKhToh467bxJ6PXxPZ+A3Kt4Xg7GIFTo6XiwA8WNndGUfCa0h+uLwiCAABIw40qKJlOwbdSOVzFlylIGaaWd8S/EYrVJJu4DDB08sfaglGeai6esqQuSZDwQZkLTEkJXPq6Q+Bjs5tNZpZs5TeLpuu6QREvnecItULPmKDkrNVmAgahXsmBREzlkcKpMrne5A5NnBlaTCziYY4o5oNtXs1nwXGJ3GnaRq8rzLB6K+BnkpKXhET5BPocywJYLaHICiWlQ0x4FG4Al++Ns9BSwLtLeq8AeY4GH0uyzmDKlI3pjxhazoL0hW4eznaCFoHe2mNo+mzylkS6krm1650RAN4vqH+0I+Lh6Odf0RzJVp4jZZpkjVYFgW3BY+oRwZPVRqg/BPWGR40IMvRAvEnMRok6xjlpFiqCzYw2vKVTd2DUjhLCirtDuP3EYhWOqQvq8y2dABHG989Zjqqxzz3xLKvQq// hcA8M1GU 8uY83UdxwPjIYxIn/fM3V33LBIKGjJ8oW9X6pKTMJCap8iEsM0jBfu1UpnAGneUZdEwe51DK8mX57gdzYjw3KKKXTJOJp75q4a6o1IGS1kp4r7xd/N+ZST+K5I08RcJLUIq3jNNbCy2AwIWLGrd77IP72J7rSG004ZG1loRrvf1D+30s= 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: List-Subscribe: List-Unsubscribe: On 11/1/2024 4:15 PM, Michal Hocko wrote: > On Fri 01-11-24 14:54:27, Stepanov Anatoly wrote: >> On 11/1/2024 10:35 AM, Michal Hocko wrote: >>> On Thu 31-10-24 17:37:12, Stepanov Anatoly wrote: >>>> If we consider the inheritance approach (prctl + launcher), it's fine until we need to change >>>> THP mode property for several tasks at once, in this case some batch-change approach needed. >>> >>> I do not follow. How is this any different from a single process? Or do >>> you mean to change the mode for an already running process? >>> >> yes, for already running set of processes > > Why is that preferred over setting the policy upfront? Setting the policy in advance is fine, as the first step to do. But we might not know in advance which exact policy is the most beneficial for one set of apps or another. So, i think it's better having an ability to change the policy on the fly, without app./service restart. -- Anatoly Stepanov, Huawei