linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: David Rientjes <rientjes@google.com>
To: Michal Hocko <mhocko@kernel.org>
Cc: akpm@linux-foundation.org, sergey.senozhatsky.work@gmail.com,
	mm-commits@vger.kernel.org, linux-mm@kvack.org
Subject: Re: + mm-oom-organize-oom-context-into-struct.patch added to -mm tree
Date: Wed, 15 Jul 2015 15:24:59 -0700 (PDT)	[thread overview]
Message-ID: <alpine.DEB.2.10.1507151523430.3514@chino.kir.corp.google.com> (raw)
In-Reply-To: <20150715094138.GE5101@dhcp22.suse.cz>

On Wed, 15 Jul 2015, Michal Hocko wrote:

> On Tue 14-07-15 15:54:20, Andrew Morton wrote:
> [...]
> > From: David Rientjes <rientjes@google.com>
> > Subject: mm, oom: organize oom context into struct
> > 
> > There are essential elements to an oom context that are passed around to
> > multiple functions.
> > 
> > Organize these elements into a new struct, struct oom_control, that
> > specifies the context for an oom condition.
> 
> Didn't you intend to name it oom_context so that it's less confusing wrt.
> oom_control usage in memcg?
>  

It's similar to struct compact_control in more ways than one, so I felt 
this naming was better.  No strong opinion.

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

      reply	other threads:[~2015-07-15 22:25 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <55a5931c.OSAbN+RkFn80ERhn%akpm@linux-foundation.org>
2015-07-15  9:41 ` Michal Hocko
2015-07-15 22:24   ` David Rientjes [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=alpine.DEB.2.10.1507151523430.3514@chino.kir.corp.google.com \
    --to=rientjes@google.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-mm@kvack.org \
    --cc=mhocko@kernel.org \
    --cc=mm-commits@vger.kernel.org \
    --cc=sergey.senozhatsky.work@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox