Received: by 2002:a05:7412:8d10:b0:f3:1519:9f41 with SMTP id bj16csp4761104rdb; Tue, 12 Dec 2023 08:36:08 -0800 (PST) X-Google-Smtp-Source: AGHT+IG+3zrC8JSLBb4QC4qgHQRoTGbFdouZteG7iZD12jHBJKkCEEWOBdZVp7/IonA7d0w2thLs X-Received: by 2002:a05:6a00:460c:b0:6ce:2732:1df6 with SMTP id ko12-20020a056a00460c00b006ce27321df6mr4127987pfb.48.1702398967922; Tue, 12 Dec 2023 08:36:07 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1702398967; cv=none; d=google.com; s=arc-20160816; b=fBzBBS7romwOs1xs+5+s+g1bIEvkkSWtE7CZGJfoSw2Goo5dgHInw2f3oFRV8Ynyix RCQNrZEXwgwDHoqMaHQsjyXeQZbtND4WI94ry4GltnoZpTmdYMgJKEmDzAYQZpBVGwuv oTYgdctH19iFXcrtGp7tD2V46OjIcJUdWRsMPtEiziFGv0e/8P+97lEmKub5VWjdIhS3 NezgAIq0Yl2kzu9Ol1Z4gP74t5OP8IeW5yjHASK1hfv/xHtwliIyZFCxFHnGjPR2ahVt 1N8B+0NFUjBws0dh+0jokusISKMY5tGD3p93qHytUYiCsPM7T8OUDsIm1I9PJ3MgWSqF gWuw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:in-reply-to :organization:autocrypt:from:references:cc:to:content-language :subject:user-agent:mime-version:date:message-id:dkim-signature; bh=xVHwTeWiLzgjfmL0SC7IYodxFmSq1OzkqJB5+EHpkWs=; fh=29mhO2qWDmYNQ60bbe4Ik9Usb7BAF5cIZjT3UW9l8AQ=; b=sz0K0SvfZeW+nAVcbpS2EV0h6VXNi80boPLVsDqBepuNE5Pw58dJ/M7CKGMp5DzW+N IA12jxatr8YbT5z2mNhuq0ywSOrfVS+uLPEVUXIS9+7Ieuzch22cM/oTF8rYLpaZi4QU ANjBG7xk4KtPIasrPM6lFumP4LYld0ZizSBx/ZfV0avhwCWBwKJkkmbZY/WDSnSTIB1E rWjyT2rKXElbVdK0lwP68ZSXPrSNal4cMSngraVLDEAlXPqv8FgRu8r/CZ2tOhwNnVzf 9svbUbrUIkP/cr3ZG7DAbFVyxyhz7Dnv6oBsyu8+tq1hVi/4rqfWrQPV2vHrn9jzhsoK /iuQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=A0xtjr0x; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::3:1 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 morse.vger.email (morse.vger.email. [2620:137:e000::3:1]) by mx.google.com with ESMTPS id ca14-20020a056a02068e00b005c66130e967si8088778pgb.264.2023.12.12.08.36.07 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 12 Dec 2023 08:36:07 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::3:1 as permitted sender) client-ip=2620:137:e000::3:1; Authentication-Results: mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=A0xtjr0x; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::3:1 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Received: from out1.vger.email (depot.vger.email [IPv6:2620:137:e000::3:0]) by morse.vger.email (Postfix) with ESMTP id C0A6C801B9F2; Tue, 12 Dec 2023 08:36:03 -0800 (PST) X-Virus-Status: Clean X-Virus-Scanned: clamav-milter 0.103.11 at morse.vger.email Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1346579AbjLLQff (ORCPT + 99 others); Tue, 12 Dec 2023 11:35:35 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:48744 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S232578AbjLLQfY (ORCPT ); Tue, 12 Dec 2023 11:35:24 -0500 Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.129.124]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 4F10F107 for ; Tue, 12 Dec 2023 08:35:29 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1702398928; 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=xVHwTeWiLzgjfmL0SC7IYodxFmSq1OzkqJB5+EHpkWs=; b=A0xtjr0xdmz75QpSsr8bFaQSk8oAWmYMrcs97T0nyYISppRqXKDYRSFjZlw0aJkMpHVvvr kBFynKza9ju2H1Q+rIGLJTEw5rRIfYB7ZWcJKTXuzAXu/uSuxnh+M58z0n91DyZZ9pffHb MzaxFsmkN58ZprTp+I6bB3TjtaAsSoE= Received: from mail-wr1-f69.google.com (mail-wr1-f69.google.com [209.85.221.69]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_256_GCM_SHA384) id us-mta-693-_cA6uxQ8NFe88XiEyhOfuw-1; Tue, 12 Dec 2023 11:35:26 -0500 X-MC-Unique: _cA6uxQ8NFe88XiEyhOfuw-1 Received: by mail-wr1-f69.google.com with SMTP id ffacd0b85a97d-3333aaf02b0so5352531f8f.1 for ; Tue, 12 Dec 2023 08:35:26 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1702398925; x=1703003725; h=content-transfer-encoding:in-reply-to:organization:autocrypt:from :references:cc:to:content-language:subject:user-agent:mime-version :date:message-id:x-gm-message-state:from:to:cc:subject:date :message-id:reply-to; bh=xVHwTeWiLzgjfmL0SC7IYodxFmSq1OzkqJB5+EHpkWs=; b=cqmUp4EIzeh5itiISnGx817c8iT+hm+RhJMNQLpOXOJ18k/bsbFUTHTdSdEwEeo7RO BWoON55H3jeyaqt5k43uQsnodiCbFE5XAVFORIyp4VhpOZlZxjhyXDKqoTEoIVCZtUyZ JQ6BMEib4y2Hfla4T0aQe8xFhj9yWS0oPVd+2ARBwx1NqsVSX3YicwvY3b1WvWgqZ0CB VnOM4ChgF5l2Z5CdfogAwUSsaDO4qFyL0t2wpx+shXHnmEUezOSY2saOC2Hs+Y3/Re2M qp0+2+UhHE9IKbyN5QmjgfnqTQW9j6B+LJFtVAql2IZL6YcVy/OMTCwGV+bBx/3mwfSt /8AQ== X-Gm-Message-State: AOJu0YwcJc+mUWAkNpRUUDx2fGSez2qX+mv/MkuXQ69Ndrq02D/aVaCM 7fngML7//XqF2Zvz5lrcQRBuNpi/9IFqc8gfZwCLMOvSxD4prw3blo84thj8Nr0gwJJeVgYHGHx gq2dzUbqZvKI1ERrL8DwUTiHZ X-Received: by 2002:a5d:5cc1:0:b0:333:2fd2:2ed1 with SMTP id cg1-20020a5d5cc1000000b003332fd22ed1mr2731829wrb.74.1702398925601; Tue, 12 Dec 2023 08:35:25 -0800 (PST) X-Received: by 2002:a5d:5cc1:0:b0:333:2fd2:2ed1 with SMTP id cg1-20020a5d5cc1000000b003332fd22ed1mr2731806wrb.74.1702398925130; Tue, 12 Dec 2023 08:35:25 -0800 (PST) Received: from ?IPV6:2003:cb:c74b:ca00:4ca2:ff2c:9092:f070? (p200300cbc74bca004ca2ff2c9092f070.dip0.t-ipconnect.de. [2003:cb:c74b:ca00:4ca2:ff2c:9092:f070]) by smtp.gmail.com with ESMTPSA id n4-20020a5d6b84000000b0033634aef014sm1326595wrx.104.2023.12.12.08.35.23 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 12 Dec 2023 08:35:24 -0800 (PST) Message-ID: Date: Tue, 12 Dec 2023 17:35:23 +0100 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: [PATCH v9 04/10] mm: thp: Support allocation of anonymous multi-size THP Content-Language: en-US To: Ryan Roberts , Andrew Morton , Matthew Wilcox , Yin Fengwei , Yu Zhao , Catalin Marinas , Anshuman Khandual , Yang Shi , "Huang, Ying" , Zi Yan , Luis Chamberlain , Itaru Kitayama , "Kirill A. Shutemov" , John Hubbard , David Rientjes , Vlastimil Babka , Hugh Dickins , Kefeng Wang , Barry Song <21cnbao@gmail.com>, Alistair Popple Cc: linux-mm@kvack.org, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org References: <20231207161211.2374093-1-ryan.roberts@arm.com> <20231207161211.2374093-5-ryan.roberts@arm.com> <2bebcf33-e8b7-468d-86cc-31d6eb355b66@redhat.com> From: David Hildenbrand Autocrypt: addr=david@redhat.com; keydata= xsFNBFXLn5EBEAC+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 B3JfpUqcWwE7vUaYrHG1nw54pLUoPG6sAA7Mehl3nd4pZUALHwARAQABzSREYXZpZCBIaWxk ZW5icmFuZCA8ZGF2aWRAcmVkaGF0LmNvbT7CwZgEEwEIAEICGwMGCwkIBwMCBhUIAgkKCwQW AgMBAh4BAheAAhkBFiEEG9nKrXNcTDpGDfzKTd4Q9wD/g1oFAl8Ox4kFCRKpKXgACgkQTd4Q 9wD/g1oHcA//a6Tj7SBNjFNM1iNhWUo1lxAja0lpSodSnB2g4FCZ4R61SBR4l/psBL73xktp rDHrx4aSpwkRP6Epu6mLvhlfjmkRG4OynJ5HG1gfv7RJJfnUdUM1z5kdS8JBrOhMJS2c/gPf wv1TGRq2XdMPnfY2o0CxRqpcLkx4vBODvJGl2mQyJF/gPepdDfcT8/PY9BJ7FL6Hrq1gnAo4 3Iv9qV0JiT2wmZciNyYQhmA1V6dyTRiQ4YAc31zOo2IM+xisPzeSHgw3ONY/XhYvfZ9r7W1l pNQdc2G+o4Di9NPFHQQhDw3YTRR1opJaTlRDzxYxzU6ZnUUBghxt9cwUWTpfCktkMZiPSDGd KgQBjnweV2jw9UOTxjb4LXqDjmSNkjDdQUOU69jGMUXgihvo4zhYcMX8F5gWdRtMR7DzW/YE BgVcyxNkMIXoY1aYj6npHYiNQesQlqjU6azjbH70/SXKM5tNRplgW8TNprMDuntdvV9wNkFs 9TyM02V5aWxFfI42+aivc4KEw69SE9KXwC7FSf5wXzuTot97N9Phj/Z3+jx443jo2NR34XgF 89cct7wJMjOF7bBefo0fPPZQuIma0Zym71cP61OP/i11ahNye6HGKfxGCOcs5wW9kRQEk8P9 M/k2wt3mt/fCQnuP/mWutNPt95w9wSsUyATLmtNrwccz63XOwU0EVcufkQEQAOfX3n0g0fZz 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+w6DABEBAAHCwXwEGAEIACYCGwwWIQQb2cqtc1xMOkYN/MpN3hD3 AP+DWgUCXw7HsgUJEqkpoQAKCRBN3hD3AP+DWrrpD/4qS3dyVRxDcDHIlmguXjC1Q5tZTwNB boaBTPHSy/Nksu0eY7x6HfQJ3xajVH32Ms6t1trDQmPx2iP5+7iDsb7OKAb5eOS8h+BEBDeq 3ecsQDv0fFJOA9ag5O3LLNk+3x3q7e0uo06XMaY7UHS341ozXUUI7wC7iKfoUTv03iO9El5f XpNMx/YrIMduZ2+nd9Di7o5+KIwlb2mAB9sTNHdMrXesX8eBL6T9b+MZJk+mZuPxKNVfEQMQ a5SxUEADIPQTPNvBewdeI80yeOCrN+Zzwy/Mrx9EPeu59Y5vSJOx/z6OUImD/GhX7Xvkt3kq Er5KTrJz3++B6SH9pum9PuoE/k+nntJkNMmQpR4MCBaV/J9gIOPGodDKnjdng+mXliF3Ptu6 3oxc2RCyGzTlxyMwuc2U5Q7KtUNTdDe8T0uE+9b8BLMVQDDfJjqY0VVqSUwImzTDLX9S4g/8 kC4HRcclk8hpyhY2jKGluZO0awwTIMgVEzmTyBphDg/Gx7dZU1Xf8HFuE+UZ5UDHDTnwgv7E th6RC9+WrhDNspZ9fJjKWRbveQgUFCpe1sa77LAw+XFrKmBHXp9ZVIe90RMe2tRL06BGiRZr jPrnvUsUUsjRoRNJjKKA/REq+sAnhkNPPZ/NNMjaZ5b8Tovi8C0tmxiCHaQYqj7G2rgnT0kt WNyWQQ== Organization: Red Hat In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-Spam-Status: No, score=-0.9 required=5.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS,T_SCC_BODY_TEXT_LINE autolearn=unavailable autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on morse.vger.email Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org X-Greylist: Sender passed SPF test, not delayed by milter-greylist-4.6.4 (morse.vger.email [0.0.0.0]); Tue, 12 Dec 2023 08:36:04 -0800 (PST) On 12.12.23 16:38, Ryan Roberts wrote: > On 12/12/2023 15:02, David Hildenbrand wrote: >> On 07.12.23 17:12, Ryan Roberts wrote: >>> Introduce the logic to allow THP to be configured (through the new sysfs >>> interface we just added) to allocate large folios to back anonymous >>> memory, which are larger than the base page size but smaller than >>> PMD-size. We call this new THP extension "multi-size THP" (mTHP). >>> >>> mTHP continues to be PTE-mapped, but in many cases can still provide >>> similar benefits to traditional PMD-sized THP: Page faults are >>> significantly reduced (by a factor of e.g. 4, 8, 16, etc. depending on >>> the configured order), but latency spikes are much less prominent >>> because the size of each page isn't as huge as the PMD-sized variant and >>> there is less memory to clear in each page fault. The number of per-page >>> operations (e.g. ref counting, rmap management, lru list management) are >>> also significantly reduced since those ops now become per-folio. >> >> I'll note that with always-pte-mapped-thp it will be much easier to support >> incremental page clearing (e.g., zero only parts of the folio and map the >> remainder in a pro-non-like fashion whereby we'll zero on the next page fault). >> With a PMD-sized thp, you have to eventually place/rip out page tables to >> achieve that. > > But then you lose the benefits of reduced number of page faults; reducing page > faults gives a big speed up for workloads with lots of short lived processes > like compiling. Well, you can do interesting things like "allocate order-5", but zero in order-3 chunks. You get less page faults and pay for alloc/rmap only once. But yes, all has pros and cons. [...] >> >>> >>> Some architectures also employ TLB compression mechanisms to squeeze >>> more entries in when a set of PTEs are virtually and physically >>> contiguous and approporiately aligned. In this case, TLB misses will >>> occur less often. >>> >>> The new behaviour is disabled by default, but can be enabled at runtime >>> by writing to /sys/kernel/mm/transparent_hugepage/hugepage-XXkb/enabled >>> (see documentation in previous commit). The long term aim is to change >>> the default to include suitable lower orders, but there are some risks >>> around internal fragmentation that need to be better understood first. >>> >>> Tested-by: Kefeng Wang >>> Tested-by: John Hubbard >>> Signed-off-by: Ryan Roberts >>> --- >>>   include/linux/huge_mm.h |   6 ++- >>>   mm/memory.c             | 111 ++++++++++++++++++++++++++++++++++++---- >>>   2 files changed, 106 insertions(+), 11 deletions(-) >>> >>> diff --git a/include/linux/huge_mm.h b/include/linux/huge_mm.h >>> index 609c153bae57..fa7a38a30fc6 100644 >>> --- a/include/linux/huge_mm.h >>> +++ b/include/linux/huge_mm.h >>> @@ -68,9 +68,11 @@ extern struct kobj_attribute shmem_enabled_attr; >>>   #define HPAGE_PMD_NR (1<> >> [...] >> >>> + >>> +#ifdef CONFIG_TRANSPARENT_HUGEPAGE >>> +static struct folio *alloc_anon_folio(struct vm_fault *vmf) >>> +{ >>> +    struct vm_area_struct *vma = vmf->vma; >>> +    unsigned long orders; >>> +    struct folio *folio; >>> +    unsigned long addr; >>> +    pte_t *pte; >>> +    gfp_t gfp; >>> +    int order; >>> + >>> +    /* >>> +     * If uffd is active for the vma we need per-page fault fidelity to >>> +     * maintain the uffd semantics. >>> +     */ >>> +    if (unlikely(userfaultfd_armed(vma))) >>> +        goto fallback; >>> + >>> +    /* >>> +     * Get a list of all the (large) orders below PMD_ORDER that are enabled >>> +     * for this vma. Then filter out the orders that can't be allocated over >>> +     * the faulting address and still be fully contained in the vma. >>> +     */ >>> +    orders = thp_vma_allowable_orders(vma, vma->vm_flags, false, true, true, >>> +                      BIT(PMD_ORDER) - 1); >>> +    orders = thp_vma_suitable_orders(vma, vmf->address, orders); >>> + >>> +    if (!orders) >>> +        goto fallback; >>> + >>> +    pte = pte_offset_map(vmf->pmd, vmf->address & PMD_MASK); >>> +    if (!pte) >>> +        return ERR_PTR(-EAGAIN); >>> + >>> +    /* >>> +     * Find the highest order where the aligned range is completely >>> +     * pte_none(). Note that all remaining orders will be completely >>> +     * pte_none(). >>> +     */ >>> +    order = highest_order(orders); >>> +    while (orders) { >>> +        addr = ALIGN_DOWN(vmf->address, PAGE_SIZE << order); >>> +        if (pte_range_none(pte + pte_index(addr), 1 << order)) >>> +            break; >>> +        order = next_order(&orders, order); >>> +    } >>> + >>> +    pte_unmap(pte); >>> + >>> +    /* Try allocating the highest of the remaining orders. */ >>> +    gfp = vma_thp_gfp_mask(vma); >>> +    while (orders) { >>> +        addr = ALIGN_DOWN(vmf->address, PAGE_SIZE << order); >>> +        folio = vma_alloc_folio(gfp, order, vma, addr, true); >>> +        if (folio) { >>> +            clear_huge_page(&folio->page, vmf->address, 1 << order); >>> +            return folio; >>> +        } >>> +        order = next_order(&orders, order); >>> +    } >>> + >>> +fallback: >>> +    return vma_alloc_zeroed_movable_folio(vma, vmf->address); >>> +} >>> +#else >>> +#define alloc_anon_folio(vmf) \ >>> +        vma_alloc_zeroed_movable_folio((vmf)->vma, (vmf)->address) >>> +#endif >> >> A neater alternative might be >> >> static struct folio *alloc_anon_folio(struct vm_fault *vmf) >> { >> #ifdef CONFIG_TRANSPARENT_HUGEPAGE >>     /* magic */ >> fallback: >> #endif >>     return vma_alloc_zeroed_movable_folio((vmf)->vma, (vmf)->address): >> } > > I guess beauty lies in the eye of the beholder... I don't find it much neater > personally :). But happy to make the change if you insist; what's the process > now that its in mm-unstable? Just send a patch to Andrew for squashing? That way it is clear that the fallback for thp is just what !thp does. But either is fine for me; no need to change if you disagree. -- Cheers, David / dhildenb