From: Takashi Iwai <tiwai@suse.de>
To: Russell King <rmk+alsa@arm.linux.org.uk>
Cc: Jaroslav Kysela <perex@suse.cz>,
Alsa Devel list <alsa-devel@lists.sourceforge.net>
Subject: Re: [PATCH] 1/3 Implement generic device DMA mapping support
Date: Tue, 02 Mar 2004 16:23:48 +0100 [thread overview]
Message-ID: <s5h4qt7ff23.wl@alsa2.suse.de> (raw)
In-Reply-To: <s5hwu64fmb2.wl@alsa2.suse.de>
At Mon, 01 Mar 2004 19:34:57 +0100,
I wrote:
>
> At Mon, 1 Mar 2004 18:22:24 +0000,
> Russell King wrote:
> >
> > On Mon, Mar 01, 2004 at 06:51:56PM +0100, Takashi Iwai wrote:
> > > a small concern about GFP_KERNEL is that i experienced the stall when
> > > the kernel tried to allocate large continuous pages with GFP_KERNEL,
> > > e.g. modprobe stops infinitely in the module init phase (and you
> > > cannot even interrupt that process).
> > >
> > > does dma_alloc_coherent(GFP_KERNEL) with big pages work without stall?
> >
> > It depends where the stall was coming from. Do you have any further
> > details?
>
> first of alll, i have to mention that it happend in the time of 2.4
> kernels. i've not tested with 2.6 kernels at all.
>
> a typical case was es1968 driver, which allocates the all buffer pages
> at the initialization. when __get_free_pages() for 256MB with
> GFP_KERNEL is called, it goes to sleep and never gets back. since
> the context is uninterruptible, modprobe stucks and doesn't accept
> SIGKILL.
>
> anyway, i need to this behavior again with the recent kernel.
ok, i tested the new code now.
it seems working fine without stall even for es1968 driver.
the only problem is the call traces for each allocation like:
modprobe: page allocation failure. order:8, mode:0xd0
Call Trace:
[<c013939c>] __alloc_pages+0x2ec/0x300
[<c0139418>] __get_free_pages+0x18/0x30
...
i know it's just a warning but surely it's annoying if the caller
knows the allocation may fail. it would be nice if we can shut it
up.
Takashi
-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click
next prev parent reply other threads:[~2004-03-02 15:23 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-29 22:38 [PATCH] 1/3 Implement generic device DMA mapping support Russell King
2004-02-29 22:42 ` [PATCH] 2/3 " Russell King
2004-02-29 22:43 ` [PATCH] 3/3 " Russell King
2004-03-01 15:41 ` [PATCH] 1/3 " Takashi Iwai
2004-03-01 15:38 ` Jaroslav Kysela
2004-03-01 17:45 ` Russell King
2004-03-01 17:51 ` Takashi Iwai
2004-03-01 18:22 ` Russell King
2004-03-01 18:34 ` Takashi Iwai
2004-03-01 18:44 ` Takashi Iwai
2004-03-02 15:23 ` Takashi Iwai [this message]
2004-03-02 14:09 ` Takashi Iwai
2004-03-02 14:26 ` Russell King
2004-03-02 14:38 ` Takashi Iwai
2004-03-02 14:55 ` Russell King
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=s5h4qt7ff23.wl@alsa2.suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@lists.sourceforge.net \
--cc=perex@suse.cz \
--cc=rmk+alsa@arm.linux.org.uk \
/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