Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753586AbbGAVaH (ORCPT ); Wed, 1 Jul 2015 17:30:07 -0400 Received: from mail-ig0-f179.google.com ([209.85.213.179]:35702 "EHLO mail-ig0-f179.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751106AbbGAV37 (ORCPT ); Wed, 1 Jul 2015 17:29:59 -0400 Date: Wed, 1 Jul 2015 14:29:57 -0700 (PDT) From: David Rientjes X-X-Sender: rientjes@chino.kir.corp.google.com To: Sergey Senozhatsky cc: Andrew Morton , Michal Hocko , linux-kernel@vger.kernel.org, linux-mm@kvack.org Subject: Re: [patch 1/3] mm, oom: organize oom context into struct In-Reply-To: <20150701001134.GA654@swordfish> Message-ID: References: <20150619001423.GA5628@swordfish> <20150701001134.GA654@swordfish> User-Agent: Alpine 2.10 (DEB 1266 2009-07-14) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1041 Lines: 33 On Wed, 1 Jul 2015, Sergey Senozhatsky wrote: > On (06/30/15 15:46), David Rientjes wrote: > > > > There are essential elements to an oom context that are passed around to > > > > multiple functions. > > > > > > > > Organize these elements into a new struct, struct oom_context, that > > > > specifies the context for an oom condition. > > > > > > > > > > s/oom_context/oom_control/ ? > > > > > > > I think it would be confused with the existing memory.oom_control for > > memcg. > > > > Hello David, > > Sorry, I meant that in commit message you say > > :Organize these elements into a new struct, struct oom_context, that > :specifies the context for an oom condition. > > but define and use `struct oom_control' (not `struct oom_context') > Oh, point very well taken, thank you. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/