From: Mel Gorman <mgorman@suse.de>
To: Dave Jones <davej@redhat.com>,
Linux Kernel <linux-kernel@vger.kernel.org>,
linux-mm@kvack.org
Subject: Re: decode GFP flags in oom killer output.
Date: Thu, 8 Mar 2012 16:24:41 +0000 [thread overview]
Message-ID: <20120308162441.GG17697@suse.de> (raw)
In-Reply-To: <20120307233939.GB5574@redhat.com>
On Wed, Mar 07, 2012 at 06:39:39PM -0500, Dave Jones wrote:
> Decoding these flags by hand in oom reports is tedious,
> and error-prone.
>
It's not really a proper solution but scripts/gfp-translate is less
error-prone than doing it by hand but requires that you have the kernel
source available.
--
Mel Gorman
SUSE Labs
--
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/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
WARNING: multiple messages have this Message-ID (diff)
From: Mel Gorman <mgorman@suse.de>
To: Dave Jones <davej@redhat.com>,
Linux Kernel <linux-kernel@vger.kernel.org>,
linux-mm@kvack.org
Subject: Re: decode GFP flags in oom killer output.
Date: Thu, 8 Mar 2012 16:24:41 +0000 [thread overview]
Message-ID: <20120308162441.GG17697@suse.de> (raw)
In-Reply-To: <20120307233939.GB5574@redhat.com>
On Wed, Mar 07, 2012 at 06:39:39PM -0500, Dave Jones wrote:
> Decoding these flags by hand in oom reports is tedious,
> and error-prone.
>
It's not really a proper solution but scripts/gfp-translate is less
error-prone than doing it by hand but requires that you have the kernel
source available.
--
Mel Gorman
SUSE Labs
next prev parent reply other threads:[~2012-03-08 16:24 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-07 23:39 decode GFP flags in oom killer output Dave Jones
2012-03-07 23:39 ` Dave Jones
2012-03-07 23:48 ` Michal Nazarewicz
2012-03-07 23:48 ` Michal Nazarewicz
2012-03-08 0:02 ` Dave Jones
2012-03-08 0:02 ` Dave Jones
2012-03-08 0:08 ` Michal Nazarewicz
2012-03-08 0:08 ` Michal Nazarewicz
2012-03-07 23:50 ` Jesper Juhl
2012-03-07 23:50 ` Jesper Juhl
2012-03-07 23:53 ` David Rientjes
2012-03-07 23:53 ` David Rientjes
2012-03-08 0:04 ` Joe Perches
2012-03-08 0:04 ` Joe Perches
2012-03-08 0:18 ` Michal Nazarewicz
2012-03-08 0:18 ` Michal Nazarewicz
2012-03-08 16:24 ` Mel Gorman [this message]
2012-03-08 16:24 ` Mel Gorman
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=20120308162441.GG17697@suse.de \
--to=mgorman@suse.de \
--cc=davej@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.