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 mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id EA6C1C433FE for ; Fri, 12 Nov 2021 07:43:34 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id C234460FE3 for ; Fri, 12 Nov 2021 07:43:34 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S233994AbhKLHqX (ORCPT ); Fri, 12 Nov 2021 02:46:23 -0500 Received: from us-smtp-delivery-124.mimecast.com ([170.10.133.124]:57431 "EHLO us-smtp-delivery-124.mimecast.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S233387AbhKLHqQ (ORCPT ); Fri, 12 Nov 2021 02:46:16 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1636703005; 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: in-reply-to:in-reply-to:references:references; bh=2+bbLPuvp6j+cegdNKlEPJqnoq6OmsKUa3Sntf90VmI=; b=gbA/Ns77ZiSf75JXhS+rFC3ZTasLE7WIG1evsZr7njY6xETxEHtyYvqXl7hjLy8Srya3rZ MAFtBGJlHk+ZDGT3P9dnEE6KsDG/K8pydIh9iKMLbOa2oHlI8Tutmxfd++ZSnIwgLH4Rsm BqIh8nMfJgIS8j1OClfAOLoqRUdnRRM= Received: from mail-pf1-f200.google.com (mail-pf1-f200.google.com [209.85.210.200]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-462-k1wuWBEcPnSvWsyrf8Pxpw-1; Fri, 12 Nov 2021 02:43:24 -0500 X-MC-Unique: k1wuWBEcPnSvWsyrf8Pxpw-1 Received: by mail-pf1-f200.google.com with SMTP id g142-20020a625294000000b004946d789d14so5318807pfb.3 for ; Thu, 11 Nov 2021 23:43:24 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to; bh=2+bbLPuvp6j+cegdNKlEPJqnoq6OmsKUa3Sntf90VmI=; b=7f04ip43qhy6YZwDhTudDPmf8cSog5VVSMvZ9h1RtFSPBWHqRWzuO/zToND9IkYBkC wZ8puaHhN/pDA+XczmLwCmvYPSAi1IVLADPiUvcVHA+SHs62KApiMCvDVlL4HoIHJiAb wD9tDLr5aAsdwDrx2uJ1juE7IRqz+MLotTvjXL9aln4e0LNCd/pTTkTTxlepvrM7h5zi QPt26aV8yFfY0+hwQvRKBZqO9q0FyKzgpiUE6rgRFWUmZPb227XGNhumhCXwX9KitKkN OcbXSCYJxcupajQwm8k4okccdyeMZxNbMgb3QYmq/S11gWZ5BxP2HLZYVMvu2mwCofZc LK9A== X-Gm-Message-State: AOAM531f3T9olIf7duDIJEDygSnExEgunzq6fqNTUymuwLBchh+v2AN2 8SKzBVTJ5bCH7Vu/Y9E+hshq+jByoNSIO9DKE5JE1Vd3X9lJVDIlqp5GPxNCOWpIAUOiDMgKiIv HOXUFlSZnrNHY0eePKeqcFL/j X-Received: by 2002:a62:e907:0:b0:4a0:3a71:9712 with SMTP id j7-20020a62e907000000b004a03a719712mr11992010pfh.73.1636703003574; Thu, 11 Nov 2021 23:43:23 -0800 (PST) X-Google-Smtp-Source: ABdhPJyW65zsGOp0tOg78dGWcQxPMcJVbcn+Q5ElOLrsIyJjMaVrE4YLHP5pKzdyX2p+4jQg0KZ6Bg== X-Received: by 2002:a62:e907:0:b0:4a0:3a71:9712 with SMTP id j7-20020a62e907000000b004a03a719712mr11991987pfh.73.1636703003370; Thu, 11 Nov 2021 23:43:23 -0800 (PST) Received: from xz-m1.local ([94.177.118.141]) by smtp.gmail.com with ESMTPSA id h12sm5667373pfv.117.2021.11.11.23.43.18 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 11 Nov 2021 23:43:22 -0800 (PST) Date: Fri, 12 Nov 2021 15:43:16 +0800 From: Peter Xu To: Mina Almasry Cc: David Hildenbrand , Matthew Wilcox , "Paul E . McKenney" , Yu Zhao , Jonathan Corbet , Andrew Morton , Ivan Teterevkov , Florian Schmidt , linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org, linux-mm@kvack.org Subject: Re: [PATCH v4] mm: Add PM_HUGE_THP_MAPPING to /proc/pid/pagemap Message-ID: References: <20211107235754.1395488-1-almasrymina@google.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Nov 10, 2021 at 09:50:13AM -0800, Mina Almasry wrote: > On Tue, Nov 9, 2021 at 11:03 PM Peter Xu wrote: > > > > The ending "_MAPPING" seems redundant to me, how about just call it "PM_THP" or > > "PM_HUGE" (as THP also means HUGE already)? > > > > So I want to make it clear that the flag is set only when the page is > PMD mappend and is a THP (not hugetlbfs or some other PMD device > mapping). PM_THP would imply the flag is set only if the underlying > page is THP without regard to whether it's actually PMD mapped or not. I see, that's fine. However as I mentioned I still think HUGE and THP dup with each other. Meanwhile, "MAPPING" does not sound like a boolean status on whether it's thp mapped.. If you still prefer this approach, how about PM_THP_MAPPED? -- Peter Xu