linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Bernardo Innocenti <bernie@develer.com>
To: Linux-MM@kvack.org
Subject: Fwd: uClinux 2.6.x memory allocator brokenness
Date: Sun, 17 Aug 2003 18:10:20 +0200	[thread overview]
Message-ID: <200308171810.20781.bernie@develer.com> (raw)

Hello,

even though this is an uClinux related question, perhaps it would
be best answered by the mm people since it requires in-depth knowledge
of the page allocator.

----------  Forwarded Message  ----------

Subject: uClinux 2.6.x memory allocator brokenness
Date: Saturday 16 August 2003 22:45
From: Bernardo Innocenti <bernie@develer.com>
To: uClinux development list <uclinux-dev@uclinux.org>
Cc: David McCullough <davidm@snapgear.com>, Greg Ungerer <gerg@snapgear.com>

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

-------------------------------------------------------

--
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>

                 reply	other threads:[~2003-08-17 16:10 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=200308171810.20781.bernie@develer.com \
    --to=bernie@develer.com \
    --cc=Linux-MM@kvack.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