From: Marcelo Tosatti <marcelo.tosatti@cyclades.com>
To: "Martin J. Bligh" <mbligh@mbligh.org>
Cc: James Washer <washer@trlp.com>, linux-mm@kvack.org, ak@muc.de
Subject: Re: Question about OOM-Killer
Date: Mon, 25 Jul 2005 12:46:15 -0300 [thread overview]
Message-ID: <20050725154615.GA29082@dmt.cnet> (raw)
In-Reply-To: <73740000.1122331287@flay>
On Mon, Jul 25, 2005 at 03:41:27PM -0700, Martin J. Bligh wrote:
> Jim, does seem bloody silly to be shooting stuff here, and is
> probably simple to fix ... however, would be useful to see where
> the DMA allocs are coming from as well, any chance you could dump
> a stack backtrace in __alloc_pages when we spec a mask for DMA alloc?
>
> M.
The stacktrace should probably be in mainline, along with some sort
of printk ratelimiting...
v2.4 has
if (unlikely(vm_gfp_debug))
dump_stack();
--
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:[~2005-07-25 15:46 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-18 19:21 Question about OOM-Killer James Washer
2005-07-18 19:36 ` James Washer
2005-07-23 13:00 ` Marcelo Tosatti
2005-07-25 19:11 ` James Washer
2005-07-25 12:27 ` Marcelo Tosatti
2005-07-25 22:41 ` Martin J. Bligh
2005-07-25 15:46 ` Marcelo Tosatti [this message]
2005-07-26 0:35 ` James Washer
2005-07-25 17:10 ` Marcelo Tosatti
2005-07-26 13:29 ` Martin J. Bligh
2005-07-26 15:17 ` Andi Kleen
2005-07-26 16:34 ` Martin J. Bligh
2005-07-26 16:34 ` Martin J. Bligh
2005-07-26 13:53 ` Andi Kleen
-- strict thread matches above, loose matches on Subject: below --
2023-05-31 8:42 Question about oom-killer Gou Hao
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=20050725154615.GA29082@dmt.cnet \
--to=marcelo.tosatti@cyclades.com \
--cc=ak@muc.de \
--cc=linux-mm@kvack.org \
--cc=mbligh@mbligh.org \
--cc=washer@trlp.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 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.