From: Joe Perches <joe@perches.com>
To: David Miller <davem@davemloft.net>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-usb@vger.kernel.org, linux-wireless@vger.kernel.org
Subject: Other alloc/OOM message question
Date: Fri, 08 Feb 2013 16:29:59 -0800 [thread overview]
Message-ID: <1360369799.13487.5.camel@joe-AO722> (raw)
In-Reply-To: <20130208.174500.1518593039138341685.davem@davemloft.net>
On Fri, 2013-02-08 at 17:45 -0500, David Miller wrote:
> From: Joe Perches <joe@perches.com>
> Date: Thu, 07 Feb 2013 13:46:27 -0800
> > alloc failures already get standardized OOM
> > messages and a dump_stack.
Does anyone know if all the other alloc's like
dma_alloc_coherent, dma_alloc_noncoherent,
pci_alloc_consistent always produce OOM messages
via page_alloc/warn_alloc_failed for all arches?
If so, there are many more of these OOM messages
that could be removed.
next prev parent reply other threads:[~2013-02-09 0:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-07 21:46 [PATCH] drivers: net: Remove remaining alloc/OOM messages Joe Perches
2013-02-07 22:07 ` Arend van Spriel
2013-02-07 23:29 ` Marc Kleine-Budde
2013-02-08 16:19 ` John W. Linville
2013-02-08 22:45 ` David Miller
2013-02-09 0:29 ` Joe Perches [this message]
2013-02-09 0:46 ` Other alloc/OOM message question Greg KH
[not found] ` <20130209004644.GC31290-U8xfFu+wG4EAvxtiuMwx3w@public.gmane.org>
2013-02-09 21:45 ` [RFC PATCH] dma_alloc_consistent: Remove OOM messages after failure Joe Perches
2013-02-10 7:57 ` [PATCH] drivers: net: Remove remaining alloc/OOM messages Vladimir Kondratiev
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=1360369799.13487.5.camel@joe-AO722 \
--to=joe@perches.com \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.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;
as well as URLs for NNTP newsgroup(s).