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 vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 8DAF8C32771 for ; Thu, 29 Sep 2022 03:15:23 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S234862AbiI2DPV (ORCPT ); Wed, 28 Sep 2022 23:15:21 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:46928 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S234758AbiI2DPR (ORCPT ); Wed, 28 Sep 2022 23:15:17 -0400 Received: from mail-pf1-x434.google.com (mail-pf1-x434.google.com [IPv6:2607:f8b0:4864:20::434]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id ED08EE170B for ; Wed, 28 Sep 2022 20:15:14 -0700 (PDT) Received: by mail-pf1-x434.google.com with SMTP id v186so264713pfv.11 for ; Wed, 28 Sep 2022 20:15:14 -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=KU2hDZloBHZHzc+mFThj3yY3WqkISo50/66QgTSBSqdyPF1gb82+B5prvPZBFRDnlH TusDscAp65WOLaVlxYJd65ZEcHRFTyD8MA4U70lCnTAIIJgfBKaFcNJIIC9WUEj6wRyz hHE2rhlxwsHe23jjkwsAHjlcvTXIiOdZTXe9B0Sax2mlp9tVs+Y/6H6AzckGw5tSodU2 dKUSAmwOaw7lGijGdoqdUHnOy0pKWB3ezfDrMk1zA4UrxeYl3A+4UijD9xbzlE2I43jI ReW9yZNRYK35xCJW6jNX4ZXuW0HzmEZuNDEZ/WEZayWKUFCyTYOB6q5xf7ZuVIJZVZWU /Ihw== X-Gm-Message-State: ACrzQf1QWmZzYU5L97mvAQLd+GFfI5ZKUiQ6gnEtIYBIl/PD8UlUVIB1 9ebi7uwT9k518giPoOx+AJJgIDWk6BTclw== 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 Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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?