From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-5.2 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, HEADER_FROM_DIFFERENT_DOMAINS,INCLUDES_PATCH,MAILING_LIST_MULTI,SPF_HELO_NONE, SPF_PASS,USER_AGENT_SANE_1 autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id CFCAFC432C0 for ; Fri, 22 Nov 2019 16:16:58 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 9B9712071C for ; Fri, 22 Nov 2019 16:16:58 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=cmpxchg-org.20150623.gappssmtp.com header.i=@cmpxchg-org.20150623.gappssmtp.com header.b="2CxFAF9v" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727445AbfKVQQ5 (ORCPT ); Fri, 22 Nov 2019 11:16:57 -0500 Received: from mail-pl1-f194.google.com ([209.85.214.194]:43991 "EHLO mail-pl1-f194.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726546AbfKVQQ5 (ORCPT ); Fri, 22 Nov 2019 11:16:57 -0500 Received: by mail-pl1-f194.google.com with SMTP id a18so3275739plm.10 for ; Fri, 22 Nov 2019 08:16:56 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cmpxchg-org.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:content-transfer-encoding:in-reply-to :user-agent; bh=wfrcrjX2H8D8RSvVc5LOIPsNb3WQnwmD64TJNBPNLUA=; b=2CxFAF9vQ8BbOhqPOkf+HBDvDUxib+UWq9hNW0Tg4l/6YvGcIgULwb7zDfm9mbuP/9 3/EKpUXrSdv8B03hy14QpNLhWat83HNQyn1GgIfaBTMQMmmanUe+btbssVaH8haWbOpr QqRPK10O9tUUfndkbGrdfQe1z6ITlCczduG7UJhZ6JNU7ZoQRSrIbazx85Z8h4rz26Xb 6EJVTX6A/tEz9L4CMMWPjveLs+QHDUyDxvybrIHm+D9wpJ2bnJSnESNPWmTfEoXJTO6d RHERX6f1D2fDaO/gYzRlAdEHF6PJxDPr/jbgCMQMh3Z2Fj6YG7Q5lbEYKwW7Ol6/bl7e sgEw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:content-transfer-encoding :in-reply-to:user-agent; bh=wfrcrjX2H8D8RSvVc5LOIPsNb3WQnwmD64TJNBPNLUA=; b=ubMS6vFLrsFOnFcV3LGsbqJzA83Ozft+hYimwhYc4iT0/x7BS0MzTuqEUNMuAJ1NtI 5ziUN4lbmyG5d8Eoy16XWBi5VC89tYzH/i5PJfuFH8Cd2xnlFW4cbGzFx30r62DCYcNp VJkRggRyipQ9H77qMNJQJmpNCf3W3b3Z79aP6y9t+dWo52VEN5MuVmSKGazLkxuoVVQD mZEyZvQyZK7qm4BFXmbYfWTrC3afUlcF85ryVCJzEceDFZHM/eZ1MmqeU/yihJSMuzdW Crl0Z+ranTVJsgJlKXjkPkAm8OhqAhDL/CdTPynrzL1DcZ2GNfaZyfPDomflWbXiJtBX otTg== X-Gm-Message-State: APjAAAVoxQ7Pxmvwp37VLiNXu0uGx1/XV4rHz0H1jpPaLkBkQ97K2sME /I44E9ndmkYQ+EGWB32zyHffqA== X-Google-Smtp-Source: APXvYqzTddBvl2Cxl4hWR79OGc6LvFSc0Lpv9HH5Ptn1zud7XEHq5ZxyxP4/MuJ4W/R1kultrt//VA== X-Received: by 2002:a17:90a:b28c:: with SMTP id c12mr19445564pjr.22.1574439415868; Fri, 22 Nov 2019 08:16:55 -0800 (PST) Received: from localhost ([2620:10d:c090:180::9f2b]) by smtp.gmail.com with ESMTPSA id q3sm7349049pgl.15.2019.11.22.08.16.54 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Fri, 22 Nov 2019 08:16:54 -0800 (PST) Date: Fri, 22 Nov 2019 11:16:52 -0500 From: Johannes Weiner To: Alex Shi Cc: cgroups@vger.kernel.org, linux-kernel@vger.kernel.org, linux-mm@kvack.org, akpm@linux-foundation.org, mgorman@techsingularity.net, tj@kernel.org, hughd@google.com, khlebnikov@yandex-team.ru, daniel.m.jordan@oracle.com, yang.shi@linux.alibaba.com, willy@infradead.org, shakeelb@google.com, Michal Hocko , Vladimir Davydov , Roman Gushchin , Chris Down , Thomas Gleixner , Vlastimil Babka , Qian Cai , Andrey Ryabinin , "Kirill A. Shutemov" , =?iso-8859-1?B?Suly9G1l?= Glisse , Andrea Arcangeli , David Rientjes , "Aneesh Kumar K.V" , swkhack , "Potyra, Stefan" , Mike Rapoport , Stephen Rothwell , Colin Ian King , Jason Gunthorpe , Mauro Carvalho Chehab , Peng Fan , Nikolay Borisov , Ira Weiny , Kirill Tkhai , Yafang Shao Subject: Re: [PATCH v4 3/9] mm/lru: replace pgdat lru_lock with lruvec lock Message-ID: <20191122161652.GA489821@cmpxchg.org> References: <1574166203-151975-1-git-send-email-alex.shi@linux.alibaba.com> <1574166203-151975-4-git-send-email-alex.shi@linux.alibaba.com> <20191119160456.GD382712@cmpxchg.org> <20191121220613.GB487872@cmpxchg.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: Mutt/1.12.2 (2019-09-21) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Nov 22, 2019 at 10:36:32AM +0800, Alex Shi wrote: > 在 2019/11/22 上午6:06, Johannes Weiner 写道: > > If we could restrict lock_page_lruvec() to working only on PageLRU > > pages, we could fix the problem with memory barriers. But this won't > > work for split_huge_page(), which is AFAICT the only user that needs > > to freeze the lru state of a page that could be isolated elsewhere. > > > > So AFAICS the only option is to lock out mem_cgroup_move_account() > > entirely when the lru_lock is held. Which I guess should be fine. > > I guess we can try from lock_page_memcg, is that a good start? Yes. > diff --git a/mm/memcontrol.c b/mm/memcontrol.c > index 7e6387ad01f0..f4bbbf72c5b8 100644 > --- a/mm/memcontrol.c > +++ b/mm/memcontrol.c > @@ -1224,7 +1224,7 @@ struct lruvec *mem_cgroup_page_lruvec(struct page *page, struct pglist_data *pgd > goto out; > } > > - memcg = page->mem_cgroup; > + memcg = lock_page_memcg(page); > /* > * Swapcache readahead pages are added to the LRU - and > * possibly migrated - before they are charged. test_clear_page_writeback() calls this function with that lock already held so that would deadlock. Let's keep locking in lock_page_lruvec(). lock_page_lruvec(): memcg = lock_page_memcg(page); lruvec = mem_cgroup_lruvec(page_pgdat(page), memcg); spin_lock_irqsave(&lruvec->lru_lock, *flags); return lruvec; unlock_lruvec(); spin_unlock_irqrestore(&lruvec->lru_lock); __unlock_page_memcg(lruvec_memcg(lruvec)); The lock ordering should be fine as well. But it might be a good idea to stick a might_lock(&memcg->move_lock) in lock_page_memcg() before that atomic_read() and test with lockdep enabled. But that leaves me with one more worry: compaction. We locked out charge moving now, so between that and knowing that the page is alive, we have page->mem_cgroup stable. But compaction doesn't know whether the page is alive - it comes from a pfn and finds out using PageLRU. In the current code, pgdat->lru_lock remains the same before and after the page is charged to a cgroup, so once compaction has that locked and it observes PageLRU, it can go ahead and isolate the page. But lruvec->lru_lock changes during charging, and then compaction may hold the wrong lock during isolation: compaction: generic_file_buffered_read: page_cache_alloc() !PageBuddy() lock_page_lruvec(page) lruvec = mem_cgroup_page_lruvec() spin_lock(&lruvec->lru_lock) if lruvec != mem_cgroup_page_lruvec() goto again add_to_page_cache_lru() mem_cgroup_commit_charge() page->mem_cgroup = foo lru_cache_add() __pagevec_lru_add() SetPageLRU() if PageLRU(page): __isolate_lru_page() I don't see what prevents the lruvec from changing under compaction, neither in your patches nor in Hugh's. Maybe I'm missing something?