Received: by 2002:a25:ab43:0:0:0:0:0 with SMTP id u61csp248268ybi; Fri, 7 Jun 2019 07:27:24 -0700 (PDT) X-Google-Smtp-Source: APXvYqxBrU8/FD3qheUgbwl5NUNRW/88bboQ4O28vQmA77q9Z8HqXyzY94aHHCrU1Rv1NfJs5XU+ X-Received: by 2002:a17:902:b18f:: with SMTP id s15mr57438572plr.44.1559917644330; Fri, 07 Jun 2019 07:27:24 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1559917644; cv=none; d=google.com; s=arc-20160816; b=z0GyH68h4LME9HqG258F7KOFMezd7ebui3wampX7/v8wEkC75WBZN0sxgLkBN0dGs1 WWyqL2vLMUOe743od9TlPxmeKcq4+FG0jNugGDj/5lYMk+V9Lu+9LJfqwkvZoM8zmwnG 3gtMhvf4NQKqML91XppsqRPWcsR08lxSZcIqck3XS2vOAav6wN+AJwEmtk/gweTtBIl4 sUhQglOxksPlJ7EahcUglV2OskMGkzibkVvw0jiRDtksPQYdrSiJSmc2koWAvalcmneB RYaIQP+BzJhFJiAf1Ejw4AcHYbaUn6zNLZKjXIwXH5FFHgLoz1I9ft/VZmBaK3Y2bxJG 6tLw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date; bh=IQrpfQ+m1NZt4S5yJ9zkkEMPXPEj51lrA5OK0uHFPuM=; b=PZ4k0vieo80G5Ndp+4ZG//7+vR+Qpy921tA4NrWxrh++qnyaBleMLhgVOW/fBIdyjL aWt2cdLTS5kZHC5lnZjmp9MKc2ly2OVAKrAvV1cLSjs7iwXWw/OMHJlt/4TjwRdcv2OJ 8bGlPwwwKMhASHatlmsJfhYqr0Wu6qZEf1H8oJAgvcxCRCjKPptIj09h53S+XBbxH3PS GC2/j70DOGaUQW2j0uWdf8+NiEa58s66RY9j5hzcGvkkAuxX60xpZ6aXB2IeEaFVKX+t GviWCkZD1LXqBQII0fut41Wq3CZyy5TegDpbhjDsD+187QYytcPJelquY2lOZENqDCx9 v61A== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id u1si1784785pgo.595.2019.06.07.07.27.07; Fri, 07 Jun 2019 07:27:24 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1729178AbfFGOZi (ORCPT + 99 others); Fri, 7 Jun 2019 10:25:38 -0400 Received: from mx2.suse.de ([195.135.220.15]:37140 "EHLO mx1.suse.de" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1728572AbfFGOZh (ORCPT ); Fri, 7 Jun 2019 10:25:37 -0400 X-Virus-Scanned: by amavisd-new at test-mx.suse.de Received: from relay2.suse.de (unknown [195.135.220.254]) by mx1.suse.de (Postfix) with ESMTP id 94217AF05; Fri, 7 Jun 2019 14:25:36 +0000 (UTC) Date: Fri, 7 Jun 2019 16:25:25 +0200 From: Michal Hocko To: Hugh Dickins Cc: Yang Shi , "Kirill A. Shutemov" , vbabka@suse.cz, rientjes@google.com, kirill@shutemov.name, akpm@linux-foundation.org, linux-mm@kvack.org, linux-kernel@vger.kernel.org Subject: Re: [v2 PATCH] mm: thp: fix false negative of shmem vma's THP eligibility Message-ID: <20190607142525.GH18435@dhcp22.suse.cz> References: <1556037781-57869-1-git-send-email-yang.shi@linux.alibaba.com> <20190423175252.GP25106@dhcp22.suse.cz> <5a571d64-bfce-aa04-312a-8e3547e0459a@linux.alibaba.com> <859fec1f-4b66-8c2c-98ee-2aee9358a81a@linux.alibaba.com> <20190507104709.GP31017@dhcp22.suse.cz> <217fc290-5800-31de-7d46-aa5c0f7b1c75@linux.alibaba.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.10.1 (2018-07-13) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri 07-06-19 03:57:18, Hugh Dickins wrote: [...] > The addition of "THPeligible" without an "Anon" in its name was > unfortunate. I suppose we're two releases too late to change that. Well, I do not really see any reason why THPeligible should be Anon specific at all. Even if ... > Applying process (PR_SET_THP_DISABLE) and mm (MADV_*HUGEPAGE) > limitations to shared filesystem objects doesn't work all that well. ... this is what we are going with then it is really important to have a single place to query the eligibility IMHO. > I recommend that you continue to treat shmem objects separately from > anon memory, and just make the smaps "THPeligible" more often accurate. Agreed on this. -- Michal Hocko SUSE Labs