From: "Jesper Juhl" <jesper.juhl@gmail.com>
To: "Nick Piggin" <nickpiggin@yahoo.com.au>
Cc: "Abu M. Muttalib" <abum@aftek.com>,
"Martin J. Bligh" <mbligh@mbligh.org>,
"Paulo Marques" <pmarques@grupopie.com>,
linux-kernel@vger.kernel.org
Subject: Re: Page Allocation Failure, Why?? Bug in kernel??
Date: Fri, 2 Jun 2006 09:53:59 +0200 [thread overview]
Message-ID: <9a8748490606020053m55e341a1v482c904ee7e423cf@mail.gmail.com> (raw)
In-Reply-To: <447FEC1B.80205@yahoo.com.au>
On 02/06/06, Nick Piggin <nickpiggin@yahoo.com.au> wrote:
> Abu M. Muttalib wrote:
> > Hi,
> >
> > I repeat my question, the required no of pages are available, as shown in
> > the dump produced by kernel, the request is not fulfilled. Its as follows:
> >
> > DMA: 106*4kB 11*8kB 5*16kB 3*32kB 2*64kB 1*128kB 0*256kB 0*512kB 0*1024kB =
> > 944kB
> >
> > Why this is so??
>
> Because some are kept in "emergency pools" for allocators that cannot
> sleep trying to free up memory.
>
> Teach the sound driver to use smaller buffers or just insert it at boot
> and leave it inserted. Why are you removing it then reinserting it?
>
Or, if the driver just need 32 pages that *appear* to be contiguous
without actually having to be physically contiguous, then allocate the
space with vmalloc(). Not always possible ofcourse, but if it is for
Abu's use, then perhaps that could be a solution.
--
Jesper Juhl <jesper.juhl@gmail.com>
Don't top-post http://www.catb.org/~esr/jargon/html/T/top-post.html
Plain text mails only, please http://www.expita.com/nomime.html
next prev parent reply other threads:[~2006-06-02 7:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-01 9:26 Abu M. Muttalib
2006-06-01 13:25 ` Paulo Marques
2006-06-01 13:51 ` Abu M. Muttalib
2006-06-01 14:59 ` Martin J. Bligh
2006-06-02 6:26 ` Abu M. Muttalib
2006-06-02 7:05 ` Jesper Juhl
2006-06-02 7:21 ` Abu M. Muttalib
2006-06-02 7:39 ` Dave Airlie
2006-06-02 7:43 ` Nick Piggin
2006-06-02 7:53 ` Jesper Juhl [this message]
2006-06-02 8:41 ` Abu M. Muttalib
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=9a8748490606020053m55e341a1v482c904ee7e423cf@mail.gmail.com \
--to=jesper.juhl@gmail.com \
--cc=abum@aftek.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mbligh@mbligh.org \
--cc=nickpiggin@yahoo.com.au \
--cc=pmarques@grupopie.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®