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 X-Spam-Level: X-Spam-Status: No, score=-5.6 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,INCLUDES_PATCH,MAILING_LIST_MULTI,SPF_HELO_NONE, SPF_PASS,USER_AGENT_SANE_1 autolearn=unavailable autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 66B69C32750 for ; Fri, 2 Aug 2019 11:44:44 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 3E789206A3 for ; Fri, 2 Aug 2019 11:44:44 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1564746284; bh=qf1onq6lqu0O+104lJaJ6bhxsGEz2L7fASVsvkK9p+Q=; h=Date:From:To:Cc:Subject:References:In-Reply-To:List-ID:From; b=jcy/xWY4ZG79j17Kn30YoEoB1GWZqJ6xf3FGQRvN5M+JE4Bbp2bpwDO+Eb8q5fNei RkuDYNV7U7xXrftBy+LasTlXfA4YkiGDqZK2z5aU2tE3WkKbYbLnFyrPRSv2Gvgc/B A+yWtpDJjZH6cEAxSTclpsbyhhIziaIFFlJL02IY= Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2392423AbfHBLon (ORCPT ); Fri, 2 Aug 2019 07:44:43 -0400 Received: from mx2.suse.de ([195.135.220.15]:47940 "EHLO mx1.suse.de" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1728193AbfHBLom (ORCPT ); Fri, 2 Aug 2019 07:44:42 -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 6FCAAADFC; Fri, 2 Aug 2019 11:44:40 +0000 (UTC) Date: Fri, 2 Aug 2019 13:44:38 +0200 From: Michal Hocko To: Konstantin Khlebnikov Cc: Johannes Weiner , linux-mm@kvack.org, linux-kernel@vger.kernel.org, cgroups@vger.kernel.org, Vladimir Davydov Subject: Re: [PATCH RFC] mm/memcontrol: reclaim severe usage over high limit in get_user_pages loop Message-ID: <20190802114438.GH6461@dhcp22.suse.cz> References: <156431697805.3170.6377599347542228221.stgit@buzz> <20190729154952.GC21958@cmpxchg.org> <20190729185509.GI9330@dhcp22.suse.cz> <20190802094028.GG6461@dhcp22.suse.cz> <105a2f1f-de5c-7bac-3aa5-87bd1dbcaed9@yandex-team.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <105a2f1f-de5c-7bac-3aa5-87bd1dbcaed9@yandex-team.ru> 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 02-08-19 13:01:07, Konstantin Khlebnikov wrote: > > > On 02.08.2019 12:40, Michal Hocko wrote: > > On Mon 29-07-19 20:55:09, Michal Hocko wrote: > > > On Mon 29-07-19 11:49:52, Johannes Weiner wrote: > > > > On Sun, Jul 28, 2019 at 03:29:38PM +0300, Konstantin Khlebnikov wrote: > > > > > --- a/mm/gup.c > > > > > +++ b/mm/gup.c > > > > > @@ -847,8 +847,11 @@ static long __get_user_pages(struct task_struct *tsk, struct mm_struct *mm, > > > > > ret = -ERESTARTSYS; > > > > > goto out; > > > > > } > > > > > - cond_resched(); > > > > > + /* Reclaim memory over high limit before stocking too much */ > > > > > + mem_cgroup_handle_over_high(true); > > > > > > > > I'd rather this remained part of the try_charge() call. The code > > > > comment in try_charge says this: > > > > > > > > * We can perform reclaim here if __GFP_RECLAIM but let's > > > > * always punt for simplicity and so that GFP_KERNEL can > > > > * consistently be used during reclaim. > > > > > > > > The simplicity argument doesn't hold true anymore once we have to add > > > > manual calls into allocation sites. We should instead fix try_charge() > > > > to do synchronous reclaim for __GFP_RECLAIM and only punt to userspace > > > > return when actually needed. > > > > > > Agreed. If we want to do direct reclaim on the high limit breach then it > > > should go into try_charge same way we do hard limit reclaim there. I am > > > not yet sure about how/whether to scale the excess. The only reason to > > > move reclaim to return-to-userspace path was GFP_NOWAIT charges. As you > > > say, maybe we should start by always performing the reclaim for > > > sleepable contexts first and only defer for non-sleeping requests. > > > > In other words. Something like patch below (completely untested). Could > > you give it a try Konstantin? > > This should work but also eliminate all benefits from deferred reclaim: > bigger batching and running without of any locks. Yes, but we already have to deal with for hard limit reclaim. Also I would like to see any actual data to back any more complex solution. We should definitely start simple. > After that gap between high and max will work just as reserve for atomic allocations. > > > > > diff --git a/mm/memcontrol.c b/mm/memcontrol.c > > index ba9138a4a1de..53a35c526e43 100644 > > --- a/mm/memcontrol.c > > +++ b/mm/memcontrol.c > > @@ -2429,8 +2429,12 @@ static int try_charge(struct mem_cgroup *memcg, gfp_t gfp_mask, > > schedule_work(&memcg->high_work); > > break; > > } > > - current->memcg_nr_pages_over_high += batch; > > - set_notify_resume(current); > > + if (gfpflags_allow_blocking(gfp_mask)) { > > + reclaim_high(memcg, nr_pages, GFP_KERNEL); ups, this should be s@GFP_KERNEL@gfp_mask@ > > + } else { > > + current->memcg_nr_pages_over_high += batch; > > + set_notify_resume(current); > > + } > > break; > > } > > } while ((memcg = parent_mem_cgroup(memcg))); > > -- Michal Hocko SUSE Labs