Received: by 2002:ac0:a581:0:0:0:0:0 with SMTP id m1-v6csp689720imm; Fri, 22 Jun 2018 03:44:17 -0700 (PDT) X-Google-Smtp-Source: ADUXVKL4mtaJYnHJELaxGQblA+o4+PMTbQ9gs34GjeeUhGdUBnScss1D1c4RtG4j7swwNy3sYQ4g X-Received: by 2002:a17:902:7105:: with SMTP id a5-v6mr1104426pll.171.1529664257451; Fri, 22 Jun 2018 03:44:17 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1529664257; cv=none; d=google.com; s=arc-20160816; b=JZmKLGhRDjz3hx3oD+gGD606MbcVAsrmDwV+OFQyHePpPD84XuX3ajGplPO5UIiii9 vrv4DU8KIHbZWbZwLdAFMCpvzy9jYKNJchS/XVtX6F0feHX/yjEo6iMxANgPApxt4NhI LYeuwTB8F1s8eXNAkbjfiGWj6Jw4SI20KqbiG76u+NbswLBCRWrFBX/AXPUppw9I6CGP 5x41pr8zFHin9iubAdqoExu9DNgs+LirObpOPIIjw6KJ8rEEx5K+gFIi0JtIAF22WFQf wDbyfCoQhK+TCH60fjfxYP1PPeEW45Z0LO0aWajjos4OrWcZVrhrj05Z96qvwLkYnNgB NgHg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-transfer-encoding:content-disposition:mime-version :references:message-id:subject:cc:to:from:date :arc-authentication-results; bh=XNd75/DPcmea61DdZ92imBnDap9mkNsL1TB5CwSy7QA=; b=l6bIsPxPsyKcy7VfV/PuWSlD5PlDGd00JooLY8PsSL2HA8N+ZXt6h9gTYvIqDvjG1K 3qQKtw64rP591UZbKnwlgxVoMl2VUQsFaKt6GlB+FNMptIYgFAMkNLp7PCwUBVZm4CUs bphHC9/7o/KkeSxgfeDTgfTe/IQ6OL9GaZ0gLcdwBy/Hr6LnDQN9hIiQV+nKbA1QB40k /55iU7Gd08l3Cr6bEdj+iIpJirLMuROfN1pFOrSB+ZWu5tFSBBXbqKP0HsMUBGcGxukj bYEVaZ2GZkMMv2dDHMZQ/0Wiv/E/Vr9J988RBbKg649pXyy6AtI5X1tYdMPDh60Aw+EG Y5vg== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id s22-v6si6028612pgs.396.2018.06.22.03.44.02; Fri, 22 Jun 2018 03:44:17 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933440AbeFVKmW (ORCPT + 99 others); Fri, 22 Jun 2018 06:42:22 -0400 Received: from mx2.suse.de ([195.135.220.15]:33493 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751338AbeFVKmU (ORCPT ); Fri, 22 Jun 2018 06:42:20 -0400 X-Virus-Scanned: by amavisd-new at test-mx.suse.de Received: from relay1.suse.de (charybdis-ext-too.suse.de [195.135.220.254]) by mx2.suse.de (Postfix) with ESMTP id 490C3AC6A; Fri, 22 Jun 2018 10:42:19 +0000 (UTC) Date: Fri, 22 Jun 2018 12:42:17 +0200 From: Michal Hocko To: =?utf-8?B?56a56Iif6ZSu?= Cc: akpm@linux-foundation.org, rientjes@google.com, kirill.shutemov@linux.intel.com, aarcange@redhat.com, penguin-kernel@i-love.sakura.ne.jp, guro@fb.com, yang.s@alibaba-inc.com, linux-mm@kvack.org, linux-kernel@vger.kernel.org, Wind Yu Subject: Re: [PATCH v9] Refactor part of the oom report in dump_header Message-ID: <20180622104217.GV10465@dhcp22.suse.cz> References: <1529056341-16182-1-git-send-email-ufo19890607@gmail.com> <20180622083949.GR10465@dhcp22.suse.cz> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: User-Agent: Mutt/1.9.5 (2018-04-13) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri 22-06-18 17:33:12, 禹舟键 wrote: > Hi Michal > > diff --git a/include/linux/oom.h b/include/linux/oom.h > > index 6adac113e96d..5bed78d4bfb8 100644 > > --- a/include/linux/oom.h > > +++ b/include/linux/oom.h > > @@ -15,6 +15,20 @@ struct notifier_block; > > struct mem_cgroup; > > struct task_struct; > > > > +enum oom_constraint { > > + CONSTRAINT_NONE, > > + CONSTRAINT_CPUSET, > > + CONSTRAINT_MEMORY_POLICY, > > + CONSTRAINT_MEMCG, > > +}; > > + > > +static const char * const oom_constraint_text[] = { > > + [CONSTRAINT_NONE] = "CONSTRAINT_NONE", > > + [CONSTRAINT_CPUSET] = "CONSTRAINT_CPUSET", > > + [CONSTRAINT_MEMORY_POLICY] = "CONSTRAINT_MEMORY_POLICY", > > + [CONSTRAINT_MEMCG] = "CONSTRAINT_MEMCG", > > +}; > > > I've suggested that this should be a separate patch. > I've separate this part in patch v7. > > [PATCH v7 1/2] Add an array of const char and enum oom_constraint in > memcontrol.h > On Sat 02-06-18 19:58:51, ufo19890607@gmail.com wrote: > >> From: yuzhoujian > >> > >> This patch will make some preparation for the follow-up patch: Refactor > >> part of the oom report in dump_header. It puts enum oom_constraint in > >> memcontrol.h and adds an array of const char for each constraint. > > > I do not get why you separate this specific part out. > > oom_constraint_text is not used in the patch. It is almost always > > preferable to have a user of newly added functionality. > > So do I need to separate this part ? You misunderstood my suggestion. Let me be more specific. Please separate the whole new oom_constraint including its _usage_. -- Michal Hocko SUSE Labs