Received: by 2002:a6b:fb09:0:0:0:0:0 with SMTP id h9csp1831158iog; Thu, 16 Jun 2022 15:03:30 -0700 (PDT) X-Google-Smtp-Source: AGRyM1sjHf//QYkS3w00AHCzI2Vt4Z5C3dpWf8u/m1tSHf2bMbzVmuIb/QUWebcahSENt7vY7vpX X-Received: by 2002:a17:902:c2c3:b0:16a:2dc:3b55 with SMTP id c3-20020a170902c2c300b0016a02dc3b55mr1134346pla.22.1655417010335; Thu, 16 Jun 2022 15:03:30 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1655417010; cv=none; d=google.com; s=arc-20160816; b=QORrevOBLFL5nCE/ltcShLjyxqSfW/NVxpCnK3VCglwQ6l5ozjQ5l/j/gxlwGHx1h3 HaqDeHaPs1vpXlPjwG3MUNd67213J8st2mlBK2kMZvnoRACcNpg/4O6fXQ4K1iJ/M75o NM9/Kk0gejYFTswggmMlHhp7pHGQsAy7c0mtDvH31DK3rS4sTulKhXAsAcTgH5tjKOfH JhVC3xHeutzKx+ChgqPJsjKD9sR80n5BW2VstqiIsa0AKSwaV450ZWJw9kmI3j5EAHgm PVSq9ZAkDpRnM37/MBxF6wraeaHQbl1SUGOafX2dLO6h84zCBPfYrpOd9NHmliZjXweG WiAg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:cc:to:subject:message-id:date:from:in-reply-to :references:mime-version:dkim-signature; bh=IjlM3vbou88b5LgLylvLtPzb4A4wi5OpV/vwF2bF6vA=; b=ZW9IYxZSXQXb3mCRL4mjVA+ebNi2bYz1riTmYC/EVfhOWCFrdQC/Jp1/f2Htza8xiG vb0PNTlCb6ESSPm3O/spdipH5AMY5hjPKHNt3gwIpRKfmp+YfOaQq/lQXmPfGWNs4yhl Rc6qHJRYmzviFKpKfpVZNTSCel01BOoAvlLLfKumpD0UxHi23IIBUeSXohdOzhQGW0g1 D4Werrnv5TZG+CcwfHt3eeKjHBSVNHvNhhOaju8s1zZnvZoumuukcd9oMQlgCkV8kaiT xhHx1XDWM8Zf4I5eyoQ1z5CdCS8fjCQbd44vgg7rD2CwZ1GW6EgQcDtchqQCwdCGliDi 8OeA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@google.com header.s=20210112 header.b=luZH+ZNa; 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; dmarc=pass (p=REJECT sp=REJECT dis=NONE) header.from=google.com Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id w9-20020a170902e88900b001678a65d755si4863823plg.154.2022.06.16.15.03.14; Thu, 16 Jun 2022 15:03:30 -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=@google.com header.s=20210112 header.b=luZH+ZNa; 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; dmarc=pass (p=REJECT sp=REJECT dis=NONE) header.from=google.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1378570AbiFPV4e (ORCPT + 99 others); Thu, 16 Jun 2022 17:56:34 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:40310 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231792AbiFPV4c (ORCPT ); Thu, 16 Jun 2022 17:56:32 -0400 Received: from mail-vs1-xe34.google.com (mail-vs1-xe34.google.com [IPv6:2607:f8b0:4864:20::e34]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id E773C5D5E6 for ; Thu, 16 Jun 2022 14:56:31 -0700 (PDT) Received: by mail-vs1-xe34.google.com with SMTP id f13so2457757vsp.1 for ; Thu, 16 Jun 2022 14:56:31 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=IjlM3vbou88b5LgLylvLtPzb4A4wi5OpV/vwF2bF6vA=; b=luZH+ZNaG5KVeSHWoVUQPxhwIvaNc10bfWOshMf4MSOUNEufKJmDGhFIsXYipizIrL kvXIo35UZLhZs5NAkxN02wDob9it6O3RpNIBEOFNATLHtrk60YwH8SkXqa4KZ63SZ5ln 3K6ssQHFLWhAl3AJAkTUAQAjzmuJ3RklEZENWSps45I/F4m0teJKOHYzQd8QoFGTimjD /jA+DmwfWTmO/GKPI5aqKlAYB7BHTD+OJemVEqCa6mhcELgpgWwvzzuG1LHv9MREzpUG rhEP0ul00polFwwQtXryB9iGzIQSUBiHVlMBZz3EyCORkNC0mc8S874U5Rl21v/w7oUI VeaQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=IjlM3vbou88b5LgLylvLtPzb4A4wi5OpV/vwF2bF6vA=; b=aikJHJv0pQiZ9+xMA6teoPveEI4wwmQAb9YDUWbwMp6l294MGZRYSlxlrW0F3JyNMA tF/Flak1DH13ASJTnwn2TpMOMn1yuIPzZezonuzGNWM8BzDnKQeDT1stJNmsTm7TtSXX hBUtt/tI2R4MVwSqc0q2sxGlA0BOu5kKU6sd/vMxyPFJsYs8uvOgoVAKT+0IU0hCUxYl zN/gPD5/yMZBtWWuo4TZNIxS5d6DmcHDuUq2r6fVGT30jSrShAb75Y2I0YAF1IaZLMrS gxeoYXhrr2acfkr/i0MAvjbhWyJ4iYv+3BlxIYWVNL0lU7GghOanIdQhbgEoGX/I5Vbc A6zQ== X-Gm-Message-State: AJIora+93OdGU1mcRnErpRjQU8XSMpZgkYZSQXUyL4S1GcWY/RvYZa8S cHsSbDTdiDGk2brf4PtouwfVzfOoEkU+aRJVYaF92Q== X-Received: by 2002:a67:b907:0:b0:34b:d597:d6e8 with SMTP id q7-20020a67b907000000b0034bd597d6e8mr3230751vsn.84.1655416590903; Thu, 16 Jun 2022 14:56:30 -0700 (PDT) MIME-Version: 1.0 References: <20220518014632.922072-1-yuzhao@google.com> <20220518014632.922072-8-yuzhao@google.com> <20220607102135.GA32448@willie-the-truck> <20220607104358.GA32583@willie-the-truck> In-Reply-To: From: Yu Zhao Date: Thu, 16 Jun 2022 15:55:54 -0600 Message-ID: Subject: Re: [PATCH v11 07/14] mm: multi-gen LRU: exploit locality in rmap To: Barry Song <21cnbao@gmail.com> Cc: Linus Torvalds , Will Deacon , Andrew Morton , Linux-MM , Andi Kleen , Aneesh Kumar , Catalin Marinas , Dave Hansen , Hillf Danton , Jens Axboe , Johannes Weiner , Jonathan Corbet , Matthew Wilcox , Mel Gorman , Michael Larabel , Michal Hocko , Mike Rapoport , Peter Zijlstra , Tejun Heo , Vlastimil Babka , LAK , Linux Doc Mailing List , LKML , x86 , Kernel Page Reclaim v2 , Brian Geffon , Jan Alexander Steffens , Oleksandr Natalenko , Steven Barrett , Suleiman Souhlal , Daniel Byrne , Donald Carr , =?UTF-8?Q?Holger_Hoffst=C3=A4tte?= , Konstantin Kharlamov , Shuang Zhai , Sofia Trinh , Vaibhav Jain , huzhanyuan@oppo.com Content-Type: text/plain; charset="UTF-8" X-Spam-Status: No, score=-17.6 required=5.0 tests=BAYES_00,DKIMWL_WL_MED, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF, ENV_AND_HDR_SPF_MATCH,RCVD_IN_DNSWL_NONE,SPF_HELO_NONE,SPF_PASS, T_SCC_BODY_TEXT_LINE,USER_IN_DEF_DKIM_WL,USER_IN_DEF_SPF_WL autolearn=ham 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 On Wed, Jun 8, 2022 at 4:46 PM Barry Song <21cnbao@gmail.com> wrote: > > On Thu, Jun 9, 2022 at 3:52 AM Linus Torvalds > wrote: > > > > On Tue, Jun 7, 2022 at 5:43 PM Barry Song <21cnbao@gmail.com> wrote: > > > > > > Given we used to have a flush for clear pte young in LRU, right now we are > > > moving to nop in almost all cases for the flush unless the address becomes > > > young exactly after look_around and before ptep_clear_flush_young_notify. > > > It means we are actually dropping flush. So the question is, were we > > > overcautious? we actually don't need the flush at all even without mglru? > > > > We stopped flushing the TLB on A bit clears on x86 back in 2014. > > > > See commit b13b1d2d8692 ("x86/mm: In the PTE swapout page reclaim case > > clear the accessed bit instead of flushing the TLB"). > > This is true for x86, RISC-V, powerpc and S390. but it is not true for > most platforms. > > There was an attempt to do the same thing in arm64: > https://www.mail-archive.com/linux-kernel@vger.kernel.org/msg1793830.html > but arm64 still sent a nosync tlbi and depent on a deferred to dsb : > https://www.mail-archive.com/linux-kernel@vger.kernel.org/msg1794484.html Barry, you've already answered your own question. Without commit 07509e10dcc7 arm64: pgtable: Fix pte_accessible(): #define pte_accessible(mm, pte) \ - (mm_tlb_flush_pending(mm) ? pte_present(pte) : pte_valid_young(pte)) + (mm_tlb_flush_pending(mm) ? pte_present(pte) : pte_valid(pte)) You missed all TLB flushes for PTEs that have gone through ptep_test_and_clear_young() on the reclaim path. But most of the time, you got away with it, only occasional app crashes: https://lore.kernel.org/r/CAGsJ_4w6JjuG4rn2P=d974wBOUtXUUnaZKnx+-G6a8_mSROa+Q@mail.gmail.com/ Why?