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 Received: from kanga.kvack.org (kanga.kvack.org [205.233.56.17]) by smtp.lore.kernel.org (Postfix) with ESMTP id B6F4AC4332F for ; Mon, 21 Nov 2022 16:59:43 +0000 (UTC) Received: by kanga.kvack.org (Postfix) id 1190F6B0072; Mon, 21 Nov 2022 11:59:43 -0500 (EST) Received: by kanga.kvack.org (Postfix, from userid 40) id 0CA396B0073; Mon, 21 Nov 2022 11:59:43 -0500 (EST) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id ED2F38E0001; Mon, 21 Nov 2022 11:59:42 -0500 (EST) X-Delivered-To: linux-mm@kvack.org Received: from relay.hostedemail.com (smtprelay0017.hostedemail.com [216.40.44.17]) by kanga.kvack.org (Postfix) with ESMTP id D1D7E6B0072 for ; Mon, 21 Nov 2022 11:59:42 -0500 (EST) Received: from smtpin09.hostedemail.com (a10.router.float.18 [10.200.18.1]) by unirelay03.hostedemail.com (Postfix) with ESMTP id 8FDFAA0B54 for ; Mon, 21 Nov 2022 16:59:42 +0000 (UTC) X-FDA: 80158061004.09.5EBBC80 Received: from mail-pf1-f201.google.com (mail-pf1-f201.google.com [209.85.210.201]) by imf28.hostedemail.com (Postfix) with ESMTP id 345A3C000E for ; Mon, 21 Nov 2022 16:59:42 +0000 (UTC) Received: by mail-pf1-f201.google.com with SMTP id x11-20020a056a000bcb00b0056c6ec11eefso7848402pfu.14 for ; Mon, 21 Nov 2022 08:59:41 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20210112; h=cc:to:from:subject:message-id:references:mime-version:in-reply-to :date:from:to:cc:subject:date:message-id:reply-to; bh=d1E4/GFb9ka3QG/dqe1GLOVhL1X2renMDEhnGD/6nC4=; b=icI3QdnVXbEM9Zb9gKG4OS8A102V11jOmTdeKnZkJFoahQg4uNVCTchDDCo2oKkBsD SNLhbWrGSgPB1+eK5ksS7hZeeGnEKC+c+5Xgy6232GUS/DlRfEXQYJ8+Zwf7cyEPCsBs KvUZ1zJCSL9G+UpqjOdi2JF5vLC2iuoCyhVOBqzekSGezGiRa+yGSG9BbNZK7pjizDg2 zxhAp2Bo4znrkfnREeAaONnXRoOe6Pi05x5MJD7Sb262M533o2UBrURGmT8Gx8SCpEqa 25XAivGsGrnR1gLaYZglogvdS7b5HyNFHIZ6c4+ZPW42m/ArG3ZSE/kfOFu4Hkh/tIZO rKjw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:from:subject:message-id:references:mime-version:in-reply-to :date:x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=d1E4/GFb9ka3QG/dqe1GLOVhL1X2renMDEhnGD/6nC4=; b=Z/wlfes1sZwtw3ZzqowCH/EiDexNx9Lessx8OT2FnTs4zFP+uv8ZVmWP021mzvcxpg lKcpXQ6Na7g/lmVZHAKu6S1NssADewNaz1yEe7hDfOnnmSBlTX2ieEey21IeaScOeKQe d6OHPbZU8NqiolUzf73Cm5UF3ywx+U57A9v9x8j3pnyx5QdJ4e/PB/RgkDVU6mVmOnVU zZ6apmaJxoSI5TKdAijADDwiJyy7uRry7XpsBhJeQp/7VfviQ4LcS9v5D+rWRvqAkssK TYwY5iOC2bAVab4gMNYWspKhBz2S69QMhmEoBXmnMoyyGLwSyrn/GQL80sHFxsceGPJp LQVQ== X-Gm-Message-State: ANoB5plyVNVZQ92S6lXPIL+J7dkT3meSXMqZ+WxVzcYY5aJuO7POa22N p/fbkv6QLW69v6tg+rqzGLmDXFbEq8ySQw== X-Google-Smtp-Source: AA0mqf69hXs2A4b62Pa/iZ4hqssDJMLyatcRLiTK7Fys42pJ6eLymex3hwCZxzSrnHEGLu8Qk/UdeD2ae0FI8g== X-Received: from shakeelb.c.googlers.com ([fda3:e722:ac3:cc00:7f:e700:c0a8:262e]) (user=shakeelb job=sendgmr) by 2002:a05:6a00:330e:b0:56c:d93a:ac5f with SMTP id cq14-20020a056a00330e00b0056cd93aac5fmr3712874pfb.48.1669049980947; Mon, 21 Nov 2022 08:59:40 -0800 (PST) Date: Mon, 21 Nov 2022 16:59:38 +0000 In-Reply-To: Mime-Version: 1.0 References: <5f52de70-975-e94f-f141-543765736181@google.com> Message-ID: <20221121165938.oid3pemsfkaeq3ws@google.com> Subject: Re: [PATCH 0/3] mm,thp,rmap: rework the use of subpages_mapcount From: Shakeel Butt To: Hugh Dickins Cc: Andrew Morton , Linus Torvalds , Johannes Weiner , "Kirill A. Shutemov" , Matthew Wilcox , David Hildenbrand , Vlastimil Babka , Peter Xu , Yang Shi , John Hubbard , Mike Kravetz , Sidhartha Kumar , Muchun Song , Miaohe Lin , Naoya Horiguchi , Mina Almasry , James Houghton , "Zach O'Keefe" , linux-kernel@vger.kernel.org, linux-mm@kvack.org Content-Type: text/plain; charset="us-ascii" ARC-Authentication-Results: i=1; imf28.hostedemail.com; dkim=pass header.d=google.com header.s=20210112 header.b=icI3QdnV; spf=pass (imf28.hostedemail.com: domain of 3fK57YwgKCOkdSLVPPWMRZZRWP.NZXWTYfi-XXVgLNV.ZcR@flex--shakeelb.bounces.google.com designates 209.85.210.201 as permitted sender) smtp.mailfrom=3fK57YwgKCOkdSLVPPWMRZZRWP.NZXWTYfi-XXVgLNV.ZcR@flex--shakeelb.bounces.google.com; dmarc=pass (policy=reject) header.from=google.com ARC-Seal: i=1; s=arc-20220608; d=hostedemail.com; t=1669049982; a=rsa-sha256; cv=none; b=3H1P5wxqFcScdCam9xvpVEA2+QylGiBs4U6+mT02B331sZIc6WncJlNz3znL7slOM8nvRd F01kTxE9QaZU2xohfq97Utx+0A/2SRijE+FdqQlUI8TJebgX07Gx+Ab5EsnI5s5k6/DDdc EVELywcaX/o6to8ImtuCKB/AgFxkGbo= ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=hostedemail.com; s=arc-20220608; t=1669049982; h=from:from:sender: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: in-reply-to:in-reply-to:references:references:dkim-signature; bh=d1E4/GFb9ka3QG/dqe1GLOVhL1X2renMDEhnGD/6nC4=; b=1BpXQV7SidcyUglbUMNaTtv9IXsucZXz+VuiB1JpvWTX87igjKK/Yex4o98b14iomUuxLQ qkwPfvXKN7LPG4k47bm/+ADJ1T2KbNH/+akKWu4N7+OWdVAOYvvabiOIDMZQobU+9EgAwB p1z0Ls7bF6WHTYYYPUb1Cj8vq5lApNM= X-Rspam-User: Authentication-Results: imf28.hostedemail.com; dkim=pass header.d=google.com header.s=20210112 header.b=icI3QdnV; spf=pass (imf28.hostedemail.com: domain of 3fK57YwgKCOkdSLVPPWMRZZRWP.NZXWTYfi-XXVgLNV.ZcR@flex--shakeelb.bounces.google.com designates 209.85.210.201 as permitted sender) smtp.mailfrom=3fK57YwgKCOkdSLVPPWMRZZRWP.NZXWTYfi-XXVgLNV.ZcR@flex--shakeelb.bounces.google.com; dmarc=pass (policy=reject) header.from=google.com X-Stat-Signature: 4itoycgbwhkobkxxe6ear55h8ffyr9uw X-Rspamd-Queue-Id: 345A3C000E X-Rspamd-Server: rspam09 X-HE-Tag: 1669049981-476972 X-Bogosity: Ham, tests=bogofilter, spamicity=0.000000, version=1.2.4 Sender: owner-linux-mm@kvack.org Precedence: bulk X-Loop: owner-majordomo@kvack.org List-ID: On Fri, Nov 18, 2022 at 01:08:13AM -0800, Hugh Dickins wrote: > Linus was underwhelmed by the earlier compound mapcounts series: > this series builds on top of it (as in next-20221117) to follow > up on his suggestions - except rmap.c still using lock_page_memcg(), > since I hesitate to steal the pleasure of deletion from Johannes. > Is there a plan to remove lock_page_memcg() altogether which I missed? I am planning to make lock_page_memcg() a nop for cgroup-v2 (as it shows up in the perf profile on exit path) but if we are removing it then I should just wait.