Received: by 2002:ac0:a581:0:0:0:0:0 with SMTP id m1-v6csp785959imm; Fri, 22 Jun 2018 05:21:58 -0700 (PDT) X-Google-Smtp-Source: ADUXVKIBWBNmM40/AntROhks4/RlKUCG5IT8nGZpjGIrUZzK76PqDVvef5NUm0NUAmCRCgd4YmuW X-Received: by 2002:a63:27c6:: with SMTP id n189-v6mr1252336pgn.164.1529670117989; Fri, 22 Jun 2018 05:21:57 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1529670117; cv=none; d=google.com; s=arc-20160816; b=k3n08DAaNmXqeFITkvLnzvvb14S65loaIPMM9u3NRAyybcXy3yU+YVhZqlePAjB7SZ wAnLhU2NERajTkgrM5TDTvZyTt8tglWXRszOP3ZOaj84TdOogu5Dc2LtTw6sLXN4h+78 cLnEj21/VEnHA8MGcn7kblNFqnmyOlz/Igz+XqxnkMXuLCa5wJlaY6UHyo+1C0dwtXKe hiZ2PJ5exQM2gXch2S9F24QDzyGgsPEV9pcierA4jak0WWrz4PY4EcI59DNo+mUVXKIB 0hFI4jHPnmgbGqAKCGfbNHcspfDWUmPAdBmmaK48Uz7Kf0No7ueodBv7xna92Iqm0R10 kR6g== 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=U/KiX3/YfWHkIuY2Z21X2Mitot/kupIFSvajEvac+Wk=; b=kjN+qc2W26yQU4Eh5w70WjooUjo4sDjDFDWHQ+If/+vXStt+pRdccfYAPittzVXNki Vvo6twU/nCQXPAUzHwXNegE4MwQ0ByFh9muXj5RNTNP3HlfCUovB/H8RbSggZntKwPBj QnU6C43TF0tXXsvbPrz+0UEmtcAsbYckKPQQE6FKcQILBXnxwwNMSZN7q8HH+FAP2x+7 iB9NHDozNwD632RelZUJnmeMw5q3rA21JpNj5dI0831fVcBYE38QlID48KKhRd8BOtMR CV0vv6IANYbvMnichyINx1hia6oe0lTYYoYuDE6Yzg25FcX0s0O4i17VeB76sFdRIOsu PpWQ== 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 l61-v6si7315105plb.507.2018.06.22.05.21.42; Fri, 22 Jun 2018 05:21:57 -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 S932885AbeFVMTl (ORCPT + 99 others); Fri, 22 Jun 2018 08:19:41 -0400 Received: from mx2.suse.de ([195.135.220.15]:44492 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751163AbeFVMTk (ORCPT ); Fri, 22 Jun 2018 08:19:40 -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 D4842ADD5; Fri, 22 Jun 2018 12:19:38 +0000 (UTC) Date: Fri, 22 Jun 2018 14:19:36 +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: <20180622121936.GX10465@dhcp22.suse.cz> References: <1529056341-16182-1-git-send-email-ufo19890607@gmail.com> <20180622083949.GR10465@dhcp22.suse.cz> <20180622104217.GV10465@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 19:40:54, 禹舟键 wrote: > Hi Michal > > You misunderstood my suggestion. Let me be more specific. Please > > separate the whole new oom_constraint including its _usage_. > > Sorry for misunderstanding your words. I think you want me to separate > enum oom_constraint and static const char * const > oom_constraint_text[] to two parts, am I right ? Just split the patch into two parts. The first to add oom_constraint* and use it. And the second which adds the missing memcg information to the oom report. -- Michal Hocko SUSE Labs