Received: by 2002:a05:6358:3188:b0:123:57c1:9b43 with SMTP id q8csp321941rwd; Wed, 17 May 2023 19:26:12 -0700 (PDT) X-Google-Smtp-Source: ACHHUZ7gV8715fW+sbfFie9DpcP40qYwe4fCoQBwWLLp0CJeh8Tq92iJwaGKT77gueKqnaVIR0jU X-Received: by 2002:a17:902:e745:b0:1ae:4292:f1c0 with SMTP id p5-20020a170902e74500b001ae4292f1c0mr922268plf.47.1684376772656; Wed, 17 May 2023 19:26:12 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1684376772; cv=none; d=google.com; s=arc-20160816; b=AyC9d5vxbJ3i81ZSJyRTmJQjslhePvrsOyPHaHDdgOMx1EItsdGQZw4PlqyStC+AEb IIGTpNpYIozdv04gax90V1wqwNqlRaCFNIZyoLGWM7Bq3IA63AwTAVXX1fypCwXUowPu guPmCPBZyTs4kmx2dV24BtdelSNxU67+x3uRfEa3/AiRc7yntp7YTWopydwBI2Y6X5w1 yk/7RuQAA2w0AK2peasHarZMYBstmxir1PDNvokHAuIYWrsdHM6h8dtNMk/Pwj7ZTd99 +r46xZ0apXB30Jkgkwuw0rl0v2gybNDUEMlAw2RQQQL8Lv9mprwf2XBNAAwpzgN1tlqQ V6ig== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :references:in-reply-to:message-id:date:subject:cc:to:from :dkim-signature; bh=sKe+AGy/Knc6S6d8Do5DN/gqM9Uy00SAbxH28Kp1LUQ=; b=aLTV96yIS207YUCTWIPEXVO2seJLD+dp8SoSeQypIe3yPh1A2V7sLbWwGdRIWU1iBy usFrA4A7SSbLGo+dnZjBqduQyaOFupK9YmA6+B/T4dDq099956NvwMHJ0q6ip7kwcYUo 2cyeTL+m3c2qbIz/UVk7M/kJWwgvLyWUoRpuuTI7BMp67ii+9WtkAwMp0vF8QTsxIlbm j3Veiw0GuJKFrvnXYT9KRloC10VK9WCfVN1LZ0uPzlXg4Kr1BP3hELmwADd5cNFLs/DA x7rkIR+g3eX9l5nPKpdy9JRYtKg+2ufRpBwQqNxTCpZczIYzGpM2zjrRlYL5y5JZfVAH Jdaw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@joelfernandes.org header.s=google header.b=gpiRUjEC; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id j11-20020a170902758b00b001a95929ca08si94058pll.533.2023.05.17.19.25.58; Wed, 17 May 2023 19:26:12 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@joelfernandes.org header.s=google header.b=gpiRUjEC; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229896AbjERCTA (ORCPT + 99 others); Wed, 17 May 2023 22:19:00 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:56044 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229824AbjERCSr (ORCPT ); Wed, 17 May 2023 22:18:47 -0400 Received: from mail-qv1-xf34.google.com (mail-qv1-xf34.google.com [IPv6:2607:f8b0:4864:20::f34]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 024DC210C for ; Wed, 17 May 2023 19:18:46 -0700 (PDT) Received: by mail-qv1-xf34.google.com with SMTP id 6a1803df08f44-6238daae378so2863126d6.1 for ; Wed, 17 May 2023 19:18:45 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=joelfernandes.org; s=google; t=1684376325; x=1686968325; h=content-transfer-encoding:mime-version:references:in-reply-to :message-id:date:subject:cc:to:from:from:to:cc:subject:date :message-id:reply-to; bh=sKe+AGy/Knc6S6d8Do5DN/gqM9Uy00SAbxH28Kp1LUQ=; b=gpiRUjEC25YrRlvGt299DCLZarxkVMlPppBRMeGjpsXJgixg9Mf1V9AuFtBCGh5WIO zYyRiKyN25sNF/Dcpz8SONWOiUN5ginUd3c7nz+IsRYtc1emCT1YYGJXOzWz7hQjxiRf eGy+COuTrQdS11tlfAZg8TDkFkoBJhCtLoMlI= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1684376325; x=1686968325; h=content-transfer-encoding:mime-version:references:in-reply-to :message-id:date:subject:cc:to:from:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=sKe+AGy/Knc6S6d8Do5DN/gqM9Uy00SAbxH28Kp1LUQ=; b=jQIgLyjHPpSrl5Tu3QGr45g54zHi6eRFo3/EPi+Q4AFCNeQ/VgndEoU1lkL8kY9/8i CgHqcgoDcsoKjhrjMaLC+srrSQoY2kuPXIl2cSsCskVuit6U8GbqQtqnHF7tmz8YRP2m Yl07dFMBvVM47d/8R1MoSfISHp8xZ82MvKmmxzJNZo0e3kM5k6C7nyo6vu5PYgVuve6Y FuZogMVhqAi9N1YyMMg4SyAs9sHzhCTH64xe9XTQ665N6+/CNMP90R/d9lw8SS/QDilF 3OOOKUP9XQsmYkAXxCEamxpcMRgXC8HI2bBX8C8Vk1hFa9+4lWLwQ3JW4bpZZubMSpqo B6bA== X-Gm-Message-State: AC+VfDya4FtcQk93KGKmb3cEJ1yipYlZhjJQH+4vjZtbOec9xucMGGol 88Yrq8ZOZYvGIdZnG9evtzlGFXnOaOC5TqdFoz4= X-Received: by 2002:a05:6214:2349:b0:5e8:3496:e641 with SMTP id hu9-20020a056214234900b005e83496e641mr2657341qvb.13.1684376324809; Wed, 17 May 2023 19:18:44 -0700 (PDT) Received: from joelboxx.c.googlers.com.com (129.239.188.35.bc.googleusercontent.com. [35.188.239.129]) by smtp.gmail.com with ESMTPSA id j13-20020a05620a000d00b007577ccf566asm85082qki.93.2023.05.17.19.18.43 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 17 May 2023 19:18:44 -0700 (PDT) From: "Joel Fernandes (Google)" To: linux-kernel@vger.kernel.org Cc: "Joel Fernandes (Google)" , linux-kselftest@vger.kernel.org, linux-mm@kvack.org, Shuah Khan , Vlastimil Babka , Michal Hocko , Linus Torvalds , Lorenzo Stoakes , Kirill A Shutemov , "Liam R. Howlett" , "Paul E. McKenney" Subject: [PATCH RFC 1/4] mm/mremap: Optimize the start addresses in move_page_tables() Date: Thu, 18 May 2023 02:18:22 +0000 Message-ID: <20230518021825.712742-2-joel@joelfernandes.org> X-Mailer: git-send-email 2.40.1.606.ga4b1b128d6-goog In-Reply-To: <20230518021825.712742-1-joel@joelfernandes.org> References: <20230518021825.712742-1-joel@joelfernandes.org> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Spam-Status: No, score=-2.1 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_NONE, 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 lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Recently, we see reports [1] of a warning that triggers due to move_page_tables() doing a downward and overlapping move on a mutually-aligned offset within a PMD. By mutual alignment, I mean the source and destination addresses of the mremap are at the same offset within a PMD. This mutual alignment along with the fact that the move is downward is sufficient to cause a warning related to having an allocated PMD that does not have PTEs in it. This warning will only trigger when there is mutual alignment in the move operation. A solution, as suggested by Linus Torvalds [2], is to initiate the copy process at the PMD level whenever such alignment is present. Implementing this approach will not only prevent the warning from being triggered, but it will also optimize the operation as this method should enhance the speed of the copy process whenever there's a possibility to start copying at the PMD level. Some more points: a. The optimization can be done only when both the source and destination of the mremap do not have anything mapped below it up to a PMD boundary. I add support to detect that. b. #1 is not a problem for the call to move_page_tables() from exec.c as nothing is expected to be mapped below the source/destination. However, for non-overlapping mutually aligned moves as triggered by mremap(2), I added support for checking such cases. c. I currently only optimize for PMD moves, in the future I/we can build on this work and do PUD moves as well if there is a need for this. But I want to take it one step at a time. [1] https://lore.kernel.org/all/ZB2GTBD%2FLWTrkOiO@dhcp22.suse.cz/ [2] https://lore.kernel.org/all/CAHk-=whd7msp8reJPfeGNyt0LiySMT0egExx3TVZSX3Ok6X=9g@mail.gmail.com/ Signed-off-by: Joel Fernandes (Google) --- mm/mremap.c | 49 +++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 49 insertions(+) diff --git a/mm/mremap.c b/mm/mremap.c index 411a85682b58..d7ee3b20e170 100644 --- a/mm/mremap.c +++ b/mm/mremap.c @@ -478,6 +478,51 @@ static bool move_pgt_entry(enum pgt_entry entry, struct vm_area_struct *vma, return moved; } +/* + * A helper to check if a previous mapping exists. Required for + * move_page_tables() and realign_addr() to determine if a previous mapping + * exists before we can do realignment optimizations. + */ +static bool check_addr_in_prev(struct vm_area_struct *vma, unsigned long addr, + unsigned long mask) +{ + int addr_masked = addr & mask; + struct vm_area_struct *prev = NULL, *cur = NULL; + + /* If the masked address is within vma, there is no prev mapping of concern. */ + if (vma->vm_start <= addr_masked) + return false; + + /* + * Attempt to find vma before prev that contains the address. + * On any issue, assume the address is within a previous mapping. + * @mmap write lock is held here, so the lookup is safe. + */ + cur = find_vma_prev(vma->vm_mm, vma->vm_start, &prev); + if (!cur || cur != vma || !prev) + return true; + + /* The masked address fell within a previous mapping. */ + if (prev->vm_end > addr_masked) + return true; + + return false; +} + +/* Opportunistically realign to specified boundary for faster copy. */ +static void realign_addr(unsigned long *old_addr, struct vm_area_struct *old_vma, + unsigned long *new_addr, struct vm_area_struct *new_vma, + unsigned long mask) +{ + if ((*old_addr & ~mask) && + (*old_addr & ~mask) == (*new_addr & ~mask) && + !check_addr_in_prev(old_vma, *old_addr, mask) && + !check_addr_in_prev(new_vma, *new_addr, mask)) { + *old_addr = *old_addr & mask; + *new_addr = *new_addr & mask; + } +} + unsigned long move_page_tables(struct vm_area_struct *vma, unsigned long old_addr, struct vm_area_struct *new_vma, unsigned long new_addr, unsigned long len, @@ -493,6 +538,10 @@ unsigned long move_page_tables(struct vm_area_struct *vma, old_end = old_addr + len; + /* If possible, realign addresses to PMD boundary for faster copy. */ + if (len >= PMD_SIZE) + realign_addr(&old_addr, vma, &new_addr, new_vma, PMD_MASK); + if (is_vm_hugetlb_page(vma)) return move_hugetlb_page_tables(vma, new_vma, old_addr, new_addr, len); -- 2.40.1.606.ga4b1b128d6-goog