Message-ID: <354360d5-dce6-a11c-ee61-d41e615bfa05@shopee.com>
Date:   Tue, 7 Mar 2023 10:36:55 +0800
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:102.0)
 Gecko/20100101 Thunderbird/102.8.0
Subject: Re: [PATCH] mm: remove redundant check in handle_mm_fault
To:     David Hildenbrand <david@redhat.com>, akpm@linux-foundation.org
Cc:     linux-mm@kvack.org, linux-kernel@vger.kernel.org
References: <20230306024959.131468-1-haifeng.xu@shopee.com>
 <df3997ed-a844-597b-fbb1-154caad78543@redhat.com>
From:   Haifeng Xu <haifeng.xu@shopee.com>
In-Reply-To: <df3997ed-a844-597b-fbb1-154caad78543@redhat.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: bulk


On 2023/3/6 21:49, David Hildenbrand wrote:
> On 06.03.23 03:49, Haifeng Xu wrote:
>> mem_cgroup_oom_synchronize() has checked whether current memcg_in_oom is
>> set or not, so remove the check in handle_mm_fault().
> 
> "mem_cgroup_oom_synchronize() will returned immediately if memcg_in_oom is not set, so remove the check from handle_mm_fault()".
> 
> However, that requires now always an indirect function call -- do we care about dropping that optimization?
> 
> 

If memcg_in_oom is set, we will check it twice, one is from handle_mm_fault(), the other is from mem_cgroup_oom_synchronize(). That seems a bit redundant.

if memcg_in_oom is not set, mem_cgroup_oom_synchronize() returns directly. Though it's an indirect function call, but the time spent can be negligible 
compare to the whole mm user falut preocess. And that won't cause stack overflow error.

Thanks.