From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751514AbdJWKyz (ORCPT ); Mon, 23 Oct 2017 06:54:55 -0400 Received: from mail-wm0-f41.google.com ([74.125.82.41]:45167 "EHLO mail-wm0-f41.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751304AbdJWKyy (ORCPT ); Mon, 23 Oct 2017 06:54:54 -0400 X-Google-Smtp-Source: ABhQp+SRXrCyZQBuhqRWDuxfyT12GK6WObrAR2SEPmSkJbZMrrXqcxdAKobVhSibD5IbS+F//0mxlQ== Date: Mon, 23 Oct 2017 13:54:50 +0300 From: "Kirill A. Shutemov" To: Neha Agarwal Cc: "Kirill A. Shutemov" , Andrew Morton , Andrea Arcangeli , Johannes Weiner , Michal Hocko , Vladimir Davydov , Dan Williams , David Rientjes , Naoya Horiguchi , Mel Gorman , Vlastimil Babka , Kemi Wang , "Aneesh Kumar K.V" , Shaohua Li , linux-kernel@vger.kernel.org, linux-mm@kvack.org, cgroups@vger.kernel.org Subject: Re: [RFC PATCH] mm, thp: make deferred_split_shrinker memcg-aware Message-ID: <20171023105450.jv4qerpzlrodfws6@node.shutemov.name> References: <20171019200323.42491-1-nehaagarwal@google.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20171019200323.42491-1-nehaagarwal@google.com> User-Agent: NeoMutt/20170609 (1.8.3) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Oct 19, 2017 at 01:03:23PM -0700, Neha Agarwal wrote: > deferred_split_shrinker is NUMA aware. Making it memcg-aware if > CONFIG_MEMCG is enabled to prevent shrinking memory of memcg(s) that are > not under memory pressure. This change isolates memory pressure across > memcgs from deferred_split_shrinker perspective, by not prematurely > splitting huge pages for the memcg that is not under memory pressure. > > Note that a pte-mapped compound huge page charge is not moved to the dst > memcg on task migration. Look mem_cgroup_move_charge_pte_range() for > more information. Thus, mem_cgroup_move_account doesn't get called on > pte-mapped compound huge pages, hence we do not need to transfer the > page from source-memcg's split to destinations-memcg's split_queue. > > Tested: Ran two copies of a microbenchmark with partially unmapped > thp(s) in two separate memory cgroups. When first memory cgroup is put > under memory pressure, it's own thp(s) split. Other memcg's thp(s) > remain intact. > > Current implementation is not NUMA aware if MEMCG is compiled. If it is > important to have this shrinker both NUMA and MEMCG aware, I can work on > that. Some feedback on this front will be useful. I thin, this should be done. That's strange compromise -- memcg vs NUMA. And I think solving will help a lot with ifdefs. -- Kirill A. Shutemov