From: Christoph Hellwig <hch@lst.de>
To: Bernardo Innocenti <bernie@develer.com>
Cc: linux-mm@kvack.org, uClinux development list <uclinux-dev@uclinux.org>
Subject: Re: [uClinux-dev] uClinux 2.6.x memory allocator brokenness
Date: Sun, 17 Aug 2003 08:54:18 +0200 [thread overview]
Message-ID: <20030817065417.GA16969@lst.de> (raw)
In-Reply-To: <200308162245.16480.bernie@develer.com>
The right list for this would be linux-mm I guess..
On Sat, Aug 16, 2003 at 10:45:16PM +0200, Bernardo Innocenti wrote:
> Hello,
>
> not sure if anybody else experienced this problem. 2.5.x/2.6.x
> kernels seem to have some nasty bug in mm/page_alloc.c.
>
> When I allocate over 256KB of memory, the allocator steps into
> __alloc_pages() with order=7 and finds nothing free in the 512KB
> slab, then it splits the 1MB block in two 512MB blocks and fails
> miserably for some unknown reason.
>
> I also noticed that any allocation (even smaller ones) always
> fail in the fast path and falls down into the slowish code
> that wakes up kswapd to free some more pages.
>
> This happens because zone->pages_low is set to 512 while
> free_pages is consistently below 400 on my system.
>
> Perhaps these values would have to be retuned on embedded targets.
>
> --
> // Bernardo Innocenti - Develer S.r.l., R&D dept.
> \X/ http://www.develer.com/
>
> Please don't send Word attachments - http://www.gnu.org/philosophy/no-word-attachments.html
>
>
> _______________________________________________
> uClinux-dev mailing list
> uClinux-dev@uclinux.org
> http://mailman.uclinux.org/mailman/listinfo/uclinux-dev
> This message was resent by uclinux-dev@uclinux.org
---end quoted text---
--
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>
parent reply other threads:[~2003-08-17 6:54 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <200308162245.16480.bernie@develer.com>]
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=20030817065417.GA16969@lst.de \
--to=hch@lst.de \
--cc=bernie@develer.com \
--cc=linux-mm@kvack.org \
--cc=uclinux-dev@uclinux.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