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 Received: from kanga.kvack.org (kanga.kvack.org [205.233.56.17]) by smtp.lore.kernel.org (Postfix) with ESMTP id D294BC04A95 for ; Thu, 29 Sep 2022 03:15:19 +0000 (UTC) Received: by kanga.kvack.org (Postfix) id 3D0CA8D0002; Wed, 28 Sep 2022 23:15:19 -0400 (EDT) Received: by kanga.kvack.org (Postfix, from userid 40) id 37FB98D0001; Wed, 28 Sep 2022 23:15:19 -0400 (EDT) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id 1F9448D0002; Wed, 28 Sep 2022 23:15:19 -0400 (EDT) X-Delivered-To: linux-mm@kvack.org Received: from relay.hostedemail.com (smtprelay0010.hostedemail.com [216.40.44.10]) by kanga.kvack.org (Postfix) with ESMTP id 0D9D38D0001 for ; Wed, 28 Sep 2022 23:15:19 -0400 (EDT) Received: from smtpin16.hostedemail.com (a10.router.float.18 [10.200.18.1]) by unirelay02.hostedemail.com (Postfix) with ESMTP id D62911210C1 for ; Thu, 29 Sep 2022 03:15:18 +0000 (UTC) X-FDA: 79963657116.16.1C7C935 Received: from mail-pf1-f182.google.com (mail-pf1-f182.google.com [209.85.210.182]) by imf11.hostedemail.com (Postfix) with ESMTP id 81C3B40005 for ; Thu, 29 Sep 2022 03:15:18 +0000 (UTC) Received: by mail-pf1-f182.google.com with SMTP id a29so283991pfk.5 for ; Wed, 28 Sep 2022 20:15:15 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bytedance-com.20210112.gappssmtp.com; s=20210112; h=content-transfer-encoding:in-reply-to:from:references:cc:to :content-language:subject:user-agent:mime-version:date:message-id :from:to:cc:subject:date; bh=PPw35s/6IrjE9k5D5RV/GouQK31w+teLLRYYyCLRYOk=; b=v5ylXiRj+RiZTaBClX9KpUMT2fBnX7kdGoacLHRQ05aBEkMC9mXBSLwUVHfIfV/elX 0bL9oAQD3ekTU9lW8axHBGe68HH7uYYx2449jrqDNPJiZTTH/rNKgOBkGfz8p0UbQOKl BT3M9eRS4r2yAxFw9ncdp5TgcCuh7LMOsR/3x8LCBZB+20JFL1LeW0fvZ7mmX2YQ5X3d jodFIEaXLhIqnk286MMbQpdmtVzqC9Z1pmIUoj+4iENdT8uCfAqiBMW/IsJpUMpYBbO1 FF5UZvwanPmMgfsyo3tz3kn13iEWzo7JL+nseGutfqUb/+i5vH75tox45oyupgvzEozl pZBQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=content-transfer-encoding:in-reply-to:from:references:cc:to :content-language:subject:user-agent:mime-version:date:message-id :x-gm-message-state:from:to:cc:subject:date; bh=PPw35s/6IrjE9k5D5RV/GouQK31w+teLLRYYyCLRYOk=; b=DH3SvzNnnTHD0eL+FrsmWxW5cq9dhPvic8C3OMCoQxvYEQdx23peD3zDLpMb4BVnmK AaKTyi9apR8/XAX4xfuiIlT+m2e4Om+p2PkavTyeCFkok+Z46GzsCA7K77SFaYsMD8eq n+slsY2IQiGnpTWQoIB+BAmOg8GFpwDM7dsiSacGXU4uDj8DIXqTjIRk5q2iYW1y+5KM 1qxvECjSEbdgLXktW5iRnjD3f3nvVdGwlBxtksaOg/JOMf42ePYRJFkbUX38WhvqXxB0 mS/+YUoYWAeLKcPLxxIWAfp8yhGnymMZLW8IzSB3wOY6uUcw4ZXZIPAqhpDMHV4DaNws rshA== X-Gm-Message-State: ACrzQf0A3C+KeFUJrMENAMcZICb8cs+xmuS+degzvbfKMIUK6G9mi+7S Gz/ImiS7Igi8uIn2WyzDYkqciA== X-Google-Smtp-Source: AMsMyM5+mdugvTJsZfTCa69ObGYcnuzg1tXlm34Uz1ubbNN6jMZQH60mC3e2f+84vBtlSIZsbDkhPA== X-Received: by 2002:a65:498d:0:b0:438:8287:6a43 with SMTP id r13-20020a65498d000000b0043882876a43mr940778pgs.495.1664421314460; Wed, 28 Sep 2022 20:15:14 -0700 (PDT) Received: from [10.76.43.192] ([61.120.150.75]) by smtp.gmail.com with ESMTPSA id i7-20020a170902c94700b001754064ac31sm4588128pla.280.2022.09.28.20.15.10 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 28 Sep 2022 20:15:13 -0700 (PDT) Message-ID: <19779c13-2db4-8273-8c7e-69fd51f5b71f@bytedance.com> Date: Thu, 29 Sep 2022 11:15:07 +0800 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:91.0) Gecko/20100101 Thunderbird/91.13.1 Subject: Re: Re: [RFC PATCH v1] mm: oom: introduce cpuset oom Content-Language: en-US To: Michal Hocko , David Rientjes Cc: Zefan Li , Tejun Heo , Johannes Weiner , Andrew Morton , cgroups@vger.kernel.org, linux-kernel@vger.kernel.org, linux-mm@kvack.org References: <20220921064710.89663-1-ligang.bdlg@bytedance.com> <18621b07-256b-7da1-885a-c96dfc8244b6@google.com> From: Gang Li In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit ARC-Authentication-Results: i=1; imf11.hostedemail.com; dkim=pass header.d=bytedance-com.20210112.gappssmtp.com header.s=20210112 header.b=v5ylXiRj; spf=pass (imf11.hostedemail.com: domain of ligang.bdlg@bytedance.com designates 209.85.210.182 as permitted sender) smtp.mailfrom=ligang.bdlg@bytedance.com; dmarc=pass (policy=none) header.from=bytedance.com ARC-Seal: i=1; s=arc-20220608; d=hostedemail.com; t=1664421318; a=rsa-sha256; cv=none; b=fGic3Jd7FjqVAL6j//DEXIgKkQpkdm5+YqbQvzPtB9jb5EywjXBJm3bARON7NkIM4ky/rq jjc+mWDZiz2L4NdFGlUOINrUuya6CdmxaTHIqy4X1l+zTSkCs34sKXZL5HDk0+axx8SYEZ OL+bLXQ4HBsAU6yjanPc+XSPYZ0VNZ4= ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=hostedemail.com; s=arc-20220608; t=1664421318; h=from:from:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references:dkim-signature; bh=PPw35s/6IrjE9k5D5RV/GouQK31w+teLLRYYyCLRYOk=; b=2souZeup/dMUeysq8iA69GrYAoro9cdr7Nhuv0jyrzlb5QM+opa4QGMktoyyXij7mmPM2G V0DcwD/gl5G6SV1/eNWWYs+9Q4s3qNesnJZgvH3TJcMJsBVxMf6vcGKAPBIdEmzz9r7S2y DCRftMvBCoFeG4/3eOYyA5q5UwpjTPw= Authentication-Results: imf11.hostedemail.com; dkim=pass header.d=bytedance-com.20210112.gappssmtp.com header.s=20210112 header.b=v5ylXiRj; spf=pass (imf11.hostedemail.com: domain of ligang.bdlg@bytedance.com designates 209.85.210.182 as permitted sender) smtp.mailfrom=ligang.bdlg@bytedance.com; dmarc=pass (policy=none) header.from=bytedance.com X-Stat-Signature: sj7fh55m8gcbecskqr643mzm3w4i8tdr X-Rspamd-Queue-Id: 81C3B40005 X-Rspam-User: X-Rspamd-Server: rspam11 X-HE-Tag: 1664421318-371390 X-Bogosity: Ham, tests=bogofilter, spamicity=0.000000, version=1.2.4 Sender: owner-linux-mm@kvack.org Precedence: bulk X-Loop: owner-majordomo@kvack.org List-ID: On 2022/9/23 15:45, Michal Hocko wrote: > Yeah, that is possible and something to consider. One way to go about > that is to make the selection from all cpusets with an overlap with the > requested nodemask (probably with a preference to more constrained > ones). In any case let's keep in mind that this is a mere heuristic. We > just need to kill some process, it is not really feasible to aim for the > best selection. We should just try to reduce the harm. Our exisiting > cpuset based OOM is effectivelly random without any clear relation to > cpusets so I would be open to experimenting in this area. In addition to cpuset, users can also bind numa through mbind(). So I want to manage numa binding applications that are not managed by cpuset. Do you have any ideas?