All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: "Daniel Jacques (Alten)" <jacques.daniel@domain.hid>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai-help] rt_heap and DMA32 zone
Date: Tue, 19 Oct 2010 12:22:58 +0200	[thread overview]
Message-ID: <4CBD7182.2050500@domain.hid> (raw)
In-Reply-To: <DF9F3A3C150B0646A17FF1487C1B6D5E0380C01F@rennsmail06.eu.thmulti.com>

Daniel Jacques (Alten) wrote:
> Hi,
> 
> I noticed some allocation failure using kmalloc in case of GFP_DMA32 with big size, even if I modified the CONFIG_FORCE_MAX_ZONEORDER to be coherent with my max size (32MB).
> I don't know the reason of this failure. I am interesting by any idea about this point ...
> Meanwhile, to avoid this trouble I performed the following additional patch in ksrc/nucleus/heap.c to force using of __get_free_pages instead of kmalloc in case of GFP_DMA32 flag.
> Jacques

At this point, the problem seems to be in linux code. So, there should
be no need to modify xenomai code. Are you sure that kmalloc does not
fail due to fragmentation?

-- 
					    Gilles.


  reply	other threads:[~2010-10-19 10:22 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <DF9F3A3C150B0646A17FF1487C1B6D5E0380C00C@rennsmail06.eu.thmulti.com>
2010-10-13  7:58 ` [Xenomai-help] rt_heap and DMA32 zone Daniel Jacques (Alten)
2010-10-13  9:36   ` Gilles Chanteperdrix
2010-10-13 10:07     ` Daniel Jacques (Alten)
2010-10-13 12:36       ` Gilles Chanteperdrix
2010-10-13 13:51         ` Daniel Jacques (Alten)
2010-10-13 14:07           ` Gilles Chanteperdrix
2010-10-13 14:18             ` Gilles Chanteperdrix
2010-10-13 14:31               ` Daniel Jacques (Alten)
2010-10-14 22:29           ` Gilles Chanteperdrix
2010-10-19  9:37             ` Daniel Jacques (Alten)
2010-10-19 10:22               ` Gilles Chanteperdrix [this message]
2010-10-19 10:52                 ` Anders Blomdell

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=4CBD7182.2050500@domain.hid \
    --to=gilles.chanteperdrix@xenomai.org \
    --cc=jacques.daniel@domain.hid \
    --cc=xenomai@xenomai.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.