Received: by 2002:a25:e74b:0:0:0:0:0 with SMTP id e72csp320434ybh; Wed, 15 Jul 2020 02:53:28 -0700 (PDT) X-Google-Smtp-Source: ABdhPJxvuC63BI7Y6eHhb3hLcEgMrKM3axtkl5kWpiAbkzaCP4Tc9owFLE9IgyKQyji0YxV25Rda X-Received: by 2002:a17:907:20af:: with SMTP id pw15mr8835806ejb.204.1594806808179; Wed, 15 Jul 2020 02:53:28 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1594806808; cv=none; d=google.com; s=arc-20160816; b=yVsvTskIffPomeDA3laoOTrFsx6arYvgqtiXfLSZlNr7tFdZI+1wKeuV4uVQywKNMx xcs3TNT99OUt3olkXUU6BM2yJ+LTUHdlI6Z8+N/MhBAcHiRo3HNq1oq8uWVM99FutT1+ BTUZZuvBU3wXvRcjiEycNCrO7MOMpASGqdPjXla5a3y0tqgECv6FbM8R+RyUD3TfjbuX RxiU2JVtZG4Sr5qRUVejZvAnCJjIakHdX5EpRfNfO22L3CxcMZcSCQvQhZ3sOxgup7Ix Z5jg772U5DhyOgiaL2HXyqB0elw+i5L6SkM7DaG3/ZfYWfvmxtNRj8rNcoy99UpVfb/O swMg== 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:from:references:cc:to:subject; bh=DYEw0Zlo9yRUT+zJ4+mQsaZ/aN46BnCN9RY00/Ei8Dk=; b=s/5jXRghKt0auKq6jweB1uZVURnGp/cgjkaKl9ArOQpJCFia3a8bV8bIvOEw7fJ4sG HSGYuMefgXHz5d0xzPIQun1BO9Zyo7Z0gdtrcvR1NME1Vs6/3ZS8rzTfTq36lrTaMnkH sWjiJtuiHUdwQIJbb6S0GhnotM73v1ZhFGMXqeU8yg5Qt1f7WWkvLQATaCNArpgcGHtj F+5LIxYp9QkexlWYZuiGIrYnYtItEIr2CRDgf7neoMcP1ZswbYeBDjRt3hSy3gMFV3uE X4F8o7QKyz0CCJFAV6MXBvVLKTPfTxtm8gYNbFPlAsqw23QDmylQimQwXJnYIBAvzoV8 teqg== ARC-Authentication-Results: i=1; mx.google.com; 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 a19si967117eje.150.2020.07.15.02.53.03; Wed, 15 Jul 2020 02:53:28 -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; 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 S1730909AbgGOJvR (ORCPT + 99 others); Wed, 15 Jul 2020 05:51:17 -0400 Received: from [195.135.220.15] ([195.135.220.15]:53436 "EHLO mx2.suse.de" rhost-flags-FAIL-FAIL-OK-OK) by vger.kernel.org with ESMTP id S1730905AbgGOJvR (ORCPT ); Wed, 15 Jul 2020 05:51:17 -0400 X-Virus-Scanned: by amavisd-new at test-mx.suse.de Received: from relay2.suse.de (unknown [195.135.221.27]) by mx2.suse.de (Postfix) with ESMTP id 4F4A5AF85; Wed, 15 Jul 2020 09:51:19 +0000 (UTC) Subject: Re: [PATCH 3/4] mm/hugetlb: make hugetlb migration callback CMA aware To: js1304@gmail.com, Andrew Morton Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org, kernel-team@lge.com, Christoph Hellwig , Roman Gushchin , Mike Kravetz , Naoya Horiguchi , Michal Hocko , "Aneesh Kumar K . V" , Joonsoo Kim References: <1594789529-6206-1-git-send-email-iamjoonsoo.kim@lge.com> <1594789529-6206-3-git-send-email-iamjoonsoo.kim@lge.com> From: Vlastimil Babka Message-ID: Date: Wed, 15 Jul 2020 11:51:14 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.10.0 MIME-Version: 1.0 In-Reply-To: <1594789529-6206-3-git-send-email-iamjoonsoo.kim@lge.com> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 7/15/20 7:05 AM, js1304@gmail.com wrote: > From: Joonsoo Kim > > new_non_cma_page() in gup.c requires to allocate the new page that is not > on the CMA area. new_non_cma_page() implements it by using allocation > scope APIs. > > However, there is a work-around for hugetlb. Normal hugetlb page > allocation API for migration is alloc_huge_page_nodemask(). It consists > of two steps. First is dequeing from the pool. Second is, if there is no > available page on the queue, allocating by using the page allocator. > > new_non_cma_page() can't use this API since first step (deque) isn't > aware of scope API to exclude CMA area. So, new_non_cma_page() exports > hugetlb internal function for the second step, alloc_migrate_huge_page(), > to global scope and uses it directly. This is suboptimal since hugetlb > pages on the queue cannot be utilized. > > This patch tries to fix this situation by making the deque function on > hugetlb CMA aware. In the deque function, CMA memory is skipped if > PF_MEMALLOC_NOCMA flag is found. > > Acked-by: Mike Kravetz > Signed-off-by: Joonsoo Kim Acked-by: Vlastimil Babka