Received: by 2002:a05:6a10:22f:0:0:0:0 with SMTP id 15csp1890985pxk; Sun, 13 Sep 2020 21:16:30 -0700 (PDT) X-Google-Smtp-Source: ABdhPJy3+OGhdKZ+0NxhHJ7bnnAXlYKidgaRBzTQ86bm9T0UpkeeTdp2N0m5M/yv7OZ2oYZQfP1a X-Received: by 2002:a17:906:70d4:: with SMTP id g20mr13454502ejk.413.1600056990581; Sun, 13 Sep 2020 21:16:30 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1600056990; cv=none; d=google.com; s=arc-20160816; b=QwxSYlHbh6ywqOGhPdOAe373fOfbgmV1gVijQlfCz/f1wbWSKgeVPCUNdUIt5rZ8FE eVIjWMcM/BKh1WXDfPWk9ay7zbTSfK4vW1SnqAc12kzzrFsMXvQrQsIM1a08Y27MgLFI a8H0Kp6zctVkTDpE/kV2aEszzjVCsZo90xNc0TaGRREn93xR7KGN8kubr839N0IPpHiT DuoAu6P0RkOkYP/NH6OYaA5g9CuSne8tb8+gQXbJyHTvwLKyfSQWrbAOz/yUnTarTBVP n7wsBH9WewN45+Idw6gpfYYvaEE5Scg72Nv/EZhwaYvXoFJKxvmdNb0ARLu7woZbyL+d jALQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:in-reply-to :mime-version:user-agent:date:message-id:from:references:cc:to :subject:reply-to; bh=p5Fkl1+PZFrrkVEoTpai69gqykoptnoWa5h9BWpWFjI=; b=pygWQaJKnCueae718B+wLTFQ1idrBw04ekFOOcc/tzBmrBs9cubQ3GKsDl25yCYfBz MiKPHVRU0Bi9JCbenxoNfn+Ky7aLVh+9NK9gVdbh6IZ5nrRrU6XII3MLoqEEACkg4+ig t1AfgMeS+I/VniUi+CCiwPLBR4uclWz+6OP6GiZCiraxKlfGedtJYkoXo4hyrhrg9KPn spNQghDe5r50JAxxPmB6XWEVEVx7xyDDtIqCJUL6rFfDKIzP1pbeEUdI7eFbPs2ViVfw Twuy/KwK2oEokFmCk30q5b0ZrNG2hn1WZgiywniBFWx6zx6GkV+Avd8JcuBPoa+y3BU4 LEYQ== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=alibaba.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id oi22si6643444ejb.85.2020.09.13.21.16.08; Sun, 13 Sep 2020 21:16:30 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=alibaba.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1725994AbgINEPe (ORCPT + 99 others); Mon, 14 Sep 2020 00:15:34 -0400 Received: from out30-56.freemail.mail.aliyun.com ([115.124.30.56]:50838 "EHLO out30-56.freemail.mail.aliyun.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725974AbgINEPc (ORCPT ); Mon, 14 Sep 2020 00:15:32 -0400 X-Alimail-AntiSpam: AC=PASS;BC=-1|-1;BR=01201311R521e4;CH=green;DM=||false|;DS=||;FP=0|-1|-1|-1|0|-1|-1|-1;HT=e01e04395;MF=xlpang@linux.alibaba.com;NM=1;PH=DS;RN=9;SR=0;TI=SMTPD_---0U8ps8Kn_1600056928; Received: from xunleideMacBook-Pro.local(mailfrom:xlpang@linux.alibaba.com fp:SMTPD_---0U8ps8Kn_1600056928) by smtp.aliyun-inc.com(127.0.0.1); Mon, 14 Sep 2020 12:15:28 +0800 Reply-To: xlpang@linux.alibaba.com Subject: Re: [PATCH] mm: memcg: yield cpu when we fail to charge pages To: Julius Hemanth Pitti , hannes@cmpxchg.org, mhocko@kernel.org, vdavydov.dev@gmail.com, akpm@linux-foundation.org Cc: cgroups@vger.kernel.org, linux-mm@kvack.org, linux-kernel@vger.kernel.org, xe-linux-external@cisco.com References: <20200908185051.62420-1-jpitti@cisco.com> From: Xunlei Pang Message-ID: Date: Mon, 14 Sep 2020 12:15:27 +0800 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:68.0) Gecko/20100101 Thunderbird/68.12.0 MIME-Version: 1.0 In-Reply-To: <20200908185051.62420-1-jpitti@cisco.com> Content-Type: text/plain; charset=gbk Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 2020/9/9 AM2:50, Julius Hemanth Pitti wrote: > For non root CG, in try_charge(), we keep trying > to charge until we succeed. On non-preemptive > kernel, when we are OOM, this results in holding > CPU forever. > > On SMP systems, this doesn't create a big problem > because oom_reaper get a change to kill victim > and make some free pages. However on a single-core > CPU (or cases where oom_reaper pinned to same CPU > where try_charge is executing), oom_reaper shall > never get scheduled and we stay in try_charge forever. > > Steps to repo this on non-smp: > 1. mount -t tmpfs none /sys/fs/cgroup > 2. mkdir /sys/fs/cgroup/memory > 3. mount -t cgroup none /sys/fs/cgroup/memory -o memory > 4. mkdir /sys/fs/cgroup/memory/0 > 5. echo 40M > /sys/fs/cgroup/memory/0/memory.limit_in_bytes > 6. echo $$ > /sys/fs/cgroup/memory/0/tasks > 7. stress -m 5 --vm-bytes 10M --vm-hang 0 > > Signed-off-by: Julius Hemanth Pitti > --- > mm/memcontrol.c | 2 ++ > 1 file changed, 2 insertions(+) > > diff --git a/mm/memcontrol.c b/mm/memcontrol.c > index 0d6f3ea86738..4620d70267cb 100644 > --- a/mm/memcontrol.c > +++ b/mm/memcontrol.c > @@ -2652,6 +2652,8 @@ static int try_charge(struct mem_cgroup *memcg, gfp_t gfp_mask, > if (fatal_signal_pending(current)) > goto force; > > + cond_resched(); > + > /* > * keep retrying as long as the memcg oom killer is able to make > * a forward progress or bypass the charge if the oom killer > This should be fixed by: https://lkml.org/lkml/2020/8/26/1440 Thanks, Xunlei