From: Takashi Iwai <tiwai@suse.de>
To: Nick Piggin <nickpiggin@yahoo.com.au>
Cc: linux-mm@kvack.org
Subject: Re: OOM-killer for zone DMA?
Date: Mon, 30 Aug 2004 11:39:34 +0200 [thread overview]
Message-ID: <s5h8ybxj76x.wl@alsa2.suse.de> (raw)
In-Reply-To: <413021BA.3090908@yahoo.com.au>
At Sat, 28 Aug 2004 16:10:02 +1000,
Nick Piggin wrote:
>
> Takashi Iwai wrote:
> > Hi,
> >
> > In the primary version of my DMA allocation patch, I tried to allocate
> > pages with GFP_DMA as much as possible, then allocate with GFP_KERNEL
> > as fallback. But this doesn't work. When the zone DMA is exhausted,
> > I oberseved endless OOM-killer.
> >
> > Is this a desired behavior? I don't think triggering OOM-killer for
> > zone DMA makes sense, because apps don't allocate pages in this
> > area...
> >
>
> They easily could.
>
> > Note that the driver tried to allocate bunch of single pages with
> > GFP_DMA, not big pages, by calling dma_alloc_coherent with GFP_DMA
> > only (no __GFP_REPEAT or such modifiers).
> >
>
> You at least need __GFP_NORETRY to achieve what you want.
Yes, with that flag it can be avoided.
But it *should* retry. It's an allocation of single page, and the
caller of dma_alloc_coherent() doesn't know whether it's allocated
from zone DMA or zone normal. It sets just the coherent_dma_mask to a
value less than 32 bit.
This situation may happen even after applying my patch.
If you have more RAM than mask, allocation in the zone NORMAL may hit
the outside of mask, and tries the zone DMA as fallback, although
there are pretty enough free RAM in the zone NORMAL.
So, triggering oom-killer for zone DMA is non-sense, IMO.
Takashi
--
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:"aart@kvack.org"> aart@kvack.org </a>
next prev parent reply other threads:[~2004-08-30 9:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-27 17:02 Takashi Iwai
2004-08-27 19:01 ` Marcelo Tosatti
2004-08-28 6:04 ` William Lee Irwin III
2004-08-30 9:35 ` Takashi Iwai
2004-08-28 6:10 ` Nick Piggin
2004-08-30 9:39 ` Takashi Iwai [this message]
2004-08-30 10:36 ` Nick Piggin
2004-08-30 15:41 ` Takashi Iwai
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=s5h8ybxj76x.wl@alsa2.suse.de \
--to=tiwai@suse.de \
--cc=linux-mm@kvack.org \
--cc=nickpiggin@yahoo.com.au \
/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