From: David Rientjes <rientjes@google.com>
To: Michal Hocko <mhocko@kernel.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Jakob Unterwurzacher <jakobunt@gmail.com>,
linux-mm@kvack.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 3/4] mm, oom: organize oom context into struct
Date: Thu, 9 Jul 2015 14:09:13 -0700 (PDT) [thread overview]
Message-ID: <alpine.DEB.2.10.1507091407530.17177@chino.kir.corp.google.com> (raw)
In-Reply-To: <20150709085602.GC13872@dhcp22.suse.cz>
On Thu, 9 Jul 2015, Michal Hocko wrote:
> > > From: David Rientjes <rientjes@google.com>
> > >
> > > 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.
> > >
> > > This patch introduces no functional change.
> > >
> > > [mhocko@suse.cz: s@oom_control@oom_context@]
> > > [mhocko@suse.cz: do not initialize on stack oom_context with NULL or 0]
> > > Signed-off-by: David Rientjes <rientjes@google.com>
> > > Signed-off-by: Michal Hocko <mhocko@suse.cz>
> >
> > I hate to appear to be nacking my own patch, but it was correct when
> > included in my series
>
> What is incorrect in this patch?
Nothing, the statement is quite clear that it is also correct in my series
which is much cleaner, reduces stack usage, removes more lines of code
than yours, and organizes the oom killer code to avoid passing so many
formals which should have been done long ago.
--
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>
next prev parent reply other threads:[~2015-07-09 21:09 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-08 13:04 [PATCH 0/4] oom: sysrq+f fixes + cleanups Michal Hocko
2015-07-08 13:04 ` [PATCH 1/4] oom: Do not panic when OOM killer is sysrq triggered Michal Hocko
2015-07-08 23:36 ` David Rientjes
2015-07-09 8:23 ` Michal Hocko
2015-07-09 21:03 ` David Rientjes
2015-07-10 7:41 ` Michal Hocko
2015-07-08 13:04 ` [PATCH 2/4] oom: Do not invoke oom notifiers on sysrq+f Michal Hocko
2015-07-08 23:37 ` David Rientjes
2015-07-09 8:55 ` Michal Hocko
2015-07-09 21:07 ` David Rientjes
2015-07-10 7:40 ` Michal Hocko
2015-07-14 21:58 ` David Rientjes
2015-07-15 9:42 ` Michal Hocko
2015-07-15 22:21 ` David Rientjes
2015-07-15 22:44 ` [patch -mm] mm, oom: move oom notifiers to page allocator David Rientjes
2015-07-16 7:12 ` Michal Hocko
2015-07-08 13:04 ` [PATCH 3/4] mm, oom: organize oom context into struct Michal Hocko
2015-07-08 23:38 ` David Rientjes
2015-07-09 8:56 ` Michal Hocko
2015-07-09 21:09 ` David Rientjes [this message]
2015-07-08 13:04 ` [PATCH 4/4] oom: split out forced OOM killer Michal Hocko
2015-07-08 23:41 ` David Rientjes
2015-07-09 10:05 ` Michal Hocko
2015-07-09 21:27 ` David Rientjes
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.1507091407530.17177@chino.kir.corp.google.com \
--to=rientjes@google.com \
--cc=akpm@linux-foundation.org \
--cc=jakobunt@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.org \
/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