From: "Dave Airlie" <airlied@gmail.com>
To: "Abu M. Muttalib" <abum@aftek.com>
Cc: "Jesper Juhl" <jesper.juhl@gmail.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 17:39:44 +1000 [thread overview]
Message-ID: <21d7e9970606020039s8d2d68fq69988b6b6488722b@mail.gmail.com> (raw)
In-Reply-To: <BKEKJNIHLJDCFGDBOHGMEEJNCNAA.abum@aftek.com>
Fragmentation.
you have 32-pages scattered around the place, they are not in the one
place, you are asking for 32-contiguous pages, you cannot get this as
the memory is fragmented.
you should really never try allocating that many contiguous pages.
Dave.
On 6/2/06, Abu M. Muttalib <abum@aftek.com> 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??
>
> ~Abu.
>
> -----Original Message-----
> From: Jesper Juhl [mailto:jesper.juhl@gmail.com]
> Sent: Friday, June 02, 2006 12:36 PM
> To: Abu M. Muttalib
> Cc: Martin J. Bligh; Paulo Marques; linux-kernel@vger.kernel.org
> Subject: Re: Page Allocation Failure, Why?? Bug in kernel??
>
>
> On 02/06/06, Abu M. Muttalib <abum@aftek.com> wrote:
> > Hi,
> >
> > That's precisely I want to say. The PAGES are available but they are not
> > allocated to process. Why??
> >
> There may be 32 pages available in total, but not 32 contiguous ones -
> that's a *lot* of contiguous pages to ask for in kernel space - 128KB
> (assuming a 4096 byte page size).
>
> --
> 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
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
next prev parent reply other threads:[~2006-06-02 7:39 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 [this message]
2006-06-02 7:43 ` Nick Piggin
2006-06-02 7:53 ` Jesper Juhl
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=21d7e9970606020039s8d2d68fq69988b6b6488722b@mail.gmail.com \
--to=airlied@gmail.com \
--cc=abum@aftek.com \
--cc=jesper.juhl@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mbligh@mbligh.org \
--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®