Received: by 2002:a05:6a10:206:0:0:0:0 with SMTP id 6csp3495036pxj; Mon, 7 Jun 2021 12:05:27 -0700 (PDT) X-Google-Smtp-Source: ABdhPJzx6UKEultnp3IbjYV6YD1BexeM7f+IsTV1ErGSrfcYoZkiuut3g1BFsJUa9XUGed44NF/H X-Received: by 2002:a05:6402:26d3:: with SMTP id x19mr12709372edd.234.1623092727685; Mon, 07 Jun 2021 12:05:27 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1623092727; cv=none; d=google.com; s=arc-20160816; b=JrRhhVA7QHlIIvRVz6dPPASMEl9XIc8ocqEXSVRZDuGfwMhVH+mXylLcZM7GcsM86e arJ0cO5j9s0atfl/Pvgqe3OfSghp7gHwRwULpfS9Cl8jENt44QMqTbKgETbPiCnmGWNd uZM4RGZ7DWZru8400LxCFDHRHcbpEUUdj9wqQNtQ7AOYfE8jVrAnq7IBrsy5Ma6qFnYa MxP57bfMKzBW3niASKPJAWIwHERYEzsbhNPtTpgURTa54EeX7SKIkC9az6aMwj7z4b+R Q1j16J/FuGYzbkvREVhtWzSOECVz5mo1Esi+XDSEZtL4rY3H9N1bFBn3XLpaB9fodzlt jctg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:in-reply-to:content-disposition:mime-version :references:message-id:subject:cc:to:from:date:dkim-signature; bh=8+oQUFe+s0sTQ/Yh3GnwEeSe6epzHODQN4kobR5NKoM=; b=mfKeQUSMQgPicpGUnu+IQ1VB/KkKdlgafEBxPq7v2d1918A4Iout/cdVvCg7wU9Pmr OyKyUcpKTqJ2WUb2SS2OBFsBIRpvJ29hvDTR7uDowPyeYI8HcQ4vXtW2vPY+PObeQLay ifomUarzjL7OPmcvzxS8iESVcKN0+sOAfg8XDdDu8CIHXoINOoBEDGTSHJ0jVbIjTR5P ZYnmba1e3jH8HDQ+RelxFa1av0Ps+2isa/B2Y/aBlTO3ehAS1mQBX7n5DJZoVtjMPQpA TLm0mSQ6eQKnY/p+0YblJO1gXFhvvSHP254PlfljnrMnxNu4w9T4rUTz6rpGah14+bmr QO6A== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@suse.com header.s=susede1 header.b=PtSfcbLa; 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=pass (p=QUARANTINE sp=NONE dis=NONE) header.from=suse.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id bl4si15688007ejb.689.2021.06.07.12.05.04; Mon, 07 Jun 2021 12:05:27 -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; dkim=pass header.i=@suse.com header.s=susede1 header.b=PtSfcbLa; 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=pass (p=QUARANTINE sp=NONE dis=NONE) header.from=suse.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230328AbhFGTDT (ORCPT + 99 others); Mon, 7 Jun 2021 15:03:19 -0400 Received: from smtp-out2.suse.de ([195.135.220.29]:37964 "EHLO smtp-out2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230282AbhFGTDS (ORCPT ); Mon, 7 Jun 2021 15:03:18 -0400 Received: from relay2.suse.de (relay2.suse.de [149.44.160.134]) by smtp-out2.suse.de (Postfix) with ESMTP id 456B91FD2D; Mon, 7 Jun 2021 19:01:26 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=suse.com; s=susede1; t=1623092486; h=from:from:reply-to:date:date:message-id:message-id:to:to:cc:cc: mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=8+oQUFe+s0sTQ/Yh3GnwEeSe6epzHODQN4kobR5NKoM=; b=PtSfcbLaJobgDU1tP/2wFu7YNxsk2YOzI/uOGup4JIzfb0R/ZjmlB/XkPFCwBpDpnsOvWt X3c2eMG7yAfkZzffHvUq9l2NzvUMRCrV2eL/ply7WiG59Xb8X1RqGPmbMSNRF9gO0xbG+G Ztz/mdbgL6RNJ44Pv3a+OMOooQ48Yig= Received: from suse.cz (unknown [10.100.201.86]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by relay2.suse.de (Postfix) with ESMTPS id 12E86A3BBF; Mon, 7 Jun 2021 19:01:26 +0000 (UTC) Date: Mon, 7 Jun 2021 21:01:25 +0200 From: Michal Hocko To: Aaron Tomlin Cc: linux-mm@kvack.org, akpm@linux-foundation.org, vbabka@suse.cz, llong@redhat.com, linux-kernel@vger.kernel.org Subject: Re: [RFC PATCH] mm/oom_kill: allow oom kill allocating task for non-global case Message-ID: References: <20210607163103.632681-1-atomlin@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20210607163103.632681-1-atomlin@redhat.com> Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon 07-06-21 17:31:03, Aaron Tomlin wrote: > At the present time, in the context of memcg OOM, even when > sysctl_oom_kill_allocating_task is enabled/or set, the "allocating" > task cannot be selected, as a target for the OOM killer. > > This patch removes the restriction entirely. This is a global oom policy not a memcg specific one so a historical behavior would change. So I do not think we can change that. The policy can be implemented on the memcg level but this would require a much more detailed explanation of the usecase and the semantic (e.g. wrt. hierarchical behavior etc). > Signed-off-by: Aaron Tomlin > --- > mm/oom_kill.c | 6 +++--- > 1 file changed, 3 insertions(+), 3 deletions(-) > > diff --git a/mm/oom_kill.c b/mm/oom_kill.c > index eefd3f5fde46..3bae33e2d9c2 100644 > --- a/mm/oom_kill.c > +++ b/mm/oom_kill.c > @@ -1089,9 +1089,9 @@ bool out_of_memory(struct oom_control *oc) > oc->nodemask = NULL; > check_panic_on_oom(oc); > > - if (!is_memcg_oom(oc) && sysctl_oom_kill_allocating_task && > - current->mm && !oom_unkillable_task(current) && > - oom_cpuset_eligible(current, oc) && > + if (sysctl_oom_kill_allocating_task && current->mm && > + !oom_unkillable_task(current) && > + oom_cpuset_eligible(current, oc) && > current->signal->oom_score_adj != OOM_SCORE_ADJ_MIN) { > get_task_struct(current); > oc->chosen = current; > -- > 2.26.3 -- Michal Hocko SUSE Labs