Received: by 2002:a05:6a10:f347:0:0:0:0 with SMTP id d7csp40729pxu; Tue, 24 Nov 2020 17:58:04 -0800 (PST) X-Google-Smtp-Source: ABdhPJw1RsFKixq1zBQVzP9TWmXgkd7Mjv2T7XqKFAHfNyARHvaerx8MQUw0+cVCU4cEyFV1DsGk X-Received: by 2002:a17:906:4698:: with SMTP id a24mr1227672ejr.90.1606269484052; Tue, 24 Nov 2020 17:58:04 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1606269484; cv=none; d=google.com; s=arc-20160816; b=cKajTG7yoRH3LaRBNsIh5oOvRW8r670CXNqTtgpQLzYbocG1Bryv5ep704jROl5xnA 005y/Y5q37bmbhzKmDbjTfE8u/3/R5x0+xM7ZLJ0zsTXbwLtYeX9mLyta/5GbLv9sx4K QYsvdF/4swp73ASkB65L8zjxhfbdrwd7zyt1+DpCJEk0a7ysnmR4YVUMXORTvyaWA57p YrG+CA0bUvYqe6sJwPQLaTF982sJ+nquYBJWNy936BdVkmz9TWNTb+umFggLcRwQabUG Yen7ISP3o+HzecjWY4hnAiTbHPf3LlHnsj5dd8vPs4Ixl7+LOiDfJPKETyA0L+LIHNIS 7G2w== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:content-language :in-reply-to:mime-version:user-agent:date:message-id:organization :from:references:cc:to:subject:dkim-signature; bh=rFvnWingY7PrQj77qBtBNXevIVda9mBy5RjtelX8LV0=; b=mnbll84IGypEQMHpKp7gxt+biGx1WAIZIjmhkktoBDzFCA7zmtQdX4SCCW2sBswOMi ik1hOrhCD54cN+RDSao26rXxqc3E9FFmNrMTx2MIkBzeDsa/vNPi3znIicgmXzfMJQ+B rnYJ/bBHx1pJHNYY+judhyji9+CETDMkZV8kcvogG3YFyHkpuVsXwHmdMnASmXYMkPG3 1KD8To+S/HZwdfRP9cJ1zDPyO24MJLycu/QAxPRnP4vwHliA2jL9OjRBwV3lz5FuSeVp 2w/+UD0mRzXqJJ1f1NB6fKXSr9W/6TeTslO1xFMNn0aC30lAWIkYnksGSQVFphBaPnFw 9FwQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=bj9z1LSw; 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 a18si503659ejr.333.2020.11.24.17.57.41; Tue, 24 Nov 2020 17:58:04 -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=@redhat.com header.s=mimecast20190719 header.b=bj9z1LSw; 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 S1730814AbgKXIoq (ORCPT + 99 others); Tue, 24 Nov 2020 03:44:46 -0500 Received: from us-smtp-delivery-124.mimecast.com ([216.205.24.124]:43792 "EHLO us-smtp-delivery-124.mimecast.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1730492AbgKXIop (ORCPT ); Tue, 24 Nov 2020 03:44:45 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1606207484; 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; bh=rFvnWingY7PrQj77qBtBNXevIVda9mBy5RjtelX8LV0=; b=bj9z1LSwFtCLMkC4aDDYWJhIWfuqq2ZsL89Ni1FBKdXgSswo+J2QIQjkZd4j6jSRpChUwX 1YxgVjQjVNH3bNIJo6gA2gNu0FVw7B5PUdTSKhA/JRE9QtczFtgyxq6KJQHHBOq3QwmBPG migboDKC9eG5uDeUol1buDEfh1HfPoI= 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-147-yaL4ZV1cMG2YOctfOi8C2A-1; Tue, 24 Nov 2020 03:44:40 -0500 X-MC-Unique: yaL4ZV1cMG2YOctfOi8C2A-1 Received: from smtp.corp.redhat.com (int-mx05.intmail.prod.int.phx2.redhat.com [10.5.11.15]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id 8A6C51007293; Tue, 24 Nov 2020 08:44:37 +0000 (UTC) Received: from [10.36.113.167] (ovpn-113-167.ams2.redhat.com [10.36.113.167]) by smtp.corp.redhat.com (Postfix) with ESMTP id A77615D71D; Tue, 24 Nov 2020 08:44:34 +0000 (UTC) Subject: Re: Pinning ZONE_MOVABLE pages To: Michal Hocko , Pavel Tatashin Cc: Vlastimil Babka , linux-mm , Andrew Morton , LKML , Oscar Salvador , Dan Williams , Sasha Levin , Tyler Hicks , Joonsoo Kim , sthemmin@microsoft.com, John Hubbard References: <20201124084350.GU27488@dhcp22.suse.cz> From: David Hildenbrand Organization: Red Hat GmbH Message-ID: <43922bf4-c818-e675-2369-10097c460ac4@redhat.com> Date: Tue, 24 Nov 2020 09:44:33 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.4.0 MIME-Version: 1.0 In-Reply-To: <20201124084350.GU27488@dhcp22.suse.cz> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.79 on 10.5.11.15 Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 24.11.20 09:43, Michal Hocko wrote: > On Mon 23-11-20 11:31:59, Pavel Tatashin wrote: > [...] >> Also, we still need to take care of the fault scenario. > > Forgot to reply to this part. I believe you mean this to be fault at gup > time, right? Then the easiest way forward would be to either add yet > another scoped flag or (maybe) better to generalize memalloc_nocma_* to > imply that the allocated memory is going to be unmovable so drop > __GFP_MOVABLE and also forbid CMA. I have to admit that I do not > remember why long term pin on CMA pages is ok to go to movable but I > strongly suspect this is just shifting problem around. Agreed. -- Thanks, David / dhildenb