From: "Shilimkar, Santosh" <santosh.shilimkar@ti.com>
To: pramod gurav <pramodforum@gmail.com>, "Gupta, Ramesh" <grgupta@ti.com>
Cc: "Menon, Nishanth" <nm@ti.com>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: RE: dma_alloc_coherent fragmentation
Date: Wed, 22 Apr 2009 15:39:22 +0530 [thread overview]
Message-ID: <EAF47CD23C76F840A9E7FCE10091EFAB02B3D8F76F@dbde02.ent.ti.com> (raw)
In-Reply-To: <f502236f0904220244t6b39839aw268f0a3a7660928e@mail.gmail.com>
This would just temporarily delay the problem. People have even tried with values of 14 MB and all. Nishant M knows one such recent issue.
Bye the way use of this macro for general DMAable memory is discouraged. You can find many threads on ARM mailing list.
Regards,
Santosh
> -----Original Message-----
> From: linux-omap-owner@vger.kernel.org
> [mailto:linux-omap-owner@vger.kernel.org] On Behalf Of pramod gurav
> Sent: Wednesday, April 22, 2009 3:14 PM
> To: Gupta, Ramesh
> Cc: Menon, Nishanth; linux-omap@vger.kernel.org
> Subject: Re: dma_alloc_coherent fragmentation
>
> Hi Ramesh,
> This worked. Thanks a lot.
>
>
> --
> Best Regards
> Pramod
>
>
> On Wed, Apr 22, 2009 at 2:44 PM, Gupta, Ramesh <grgupta@ti.com> wrote:
> > Hi Pramod,
> >
> >
> >> -----Original Message-----
> >> From: linux-omap-owner@vger.kernel.org
> >> [mailto:linux-omap-owner@vger.kernel.org] On Behalf Of pramod gurav
> >> Sent: Wednesday, April 22, 2009 1:17 PM
> >> To: Menon, Nishanth
> >> Cc: linux-omap@vger.kernel.org
> >> Subject: Re: dma_alloc_coherent fragmentation
> >>
> >> Hi Nishant,
> >> I am facing the same problem to allocate a chunk of 4MB on omap3evm
> >> using dma_alloc_coherent. I used the test driver mentioned here
> >>
> http://www.mail-archive.com/linux-omap@vger.kernel.org/msg11074.html
> >>
> >> I applied the patch for
> >> ioremap(24f11ec001920f1cfaeeed8e8b55725d900bbb56) suggested by
> >> Russell, but stiill seeing the error saying
> >>
> >> coherent allocation too big (requested 0x400000 mask 0xffffffff)
> >> alloc[0] - virt=0x00000000 phy=0xFFFFFFFF size=0x00400000
> >> Allocation failed idx=0
> >> insmod: cannot insert `dummy.ko': Cannot allocate memory
> (-1): Cannot
> >> allocate memory
> >>
> >> I changed the GFP_KERNEL to GFP_TEMPORARY and also to (GFP_KERNEL |
> >> __GFP_RECLAIMABLE), but failed to insmod the module.
> >> I am working on linux-omap 2.6.28 kernel. Even I could not allocate
> >> memory size greater than 1MB.
> >> Has this been fixed? Are there any patches to fix this issue?
> >>
> >
> > What is the value for 'CONFIG_FB_OMAP_CONSISTENT_DMA_SIZE'
> (default is 2 in omap_3430sdp_defconfig), Can you please
> > try increasing to 8?
> >
> > Regards
> > Ramesh Gupta G
> >
> --
> To unsubscribe from this list: send the line "unsubscribe
> linux-omap" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
>
next prev parent reply other threads:[~2009-04-22 10:09 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-18 13:03 dma_alloc_coherent fragmentation Kamat, Nishant
2009-03-18 19:24 ` Russell King - ARM Linux
2009-03-18 20:08 ` Menon, Nishanth
2009-03-19 6:42 ` Hiroshi DOYU
2009-03-19 9:06 ` Menon, Nishanth
2009-04-22 7:46 ` pramod gurav
2009-04-22 7:50 ` Shilimkar, Santosh
2009-04-22 8:23 ` pramod gurav
2009-04-22 8:51 ` Shilimkar, Santosh
2009-04-22 9:14 ` Gupta, Ramesh
2009-04-22 9:44 ` pramod gurav
2009-04-22 10:09 ` Shilimkar, Santosh [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-03-13 15:59 Bridge issue #3! dma_alloc_coherent causing crash - pm branch Kevin Hilman
2009-03-14 4:26 ` Gupta, Ramesh
2009-03-16 9:54 ` dma_alloc_coherent bug? Menon, Nishanth
2009-03-16 17:29 ` Ameya Palande
2009-03-16 19:09 ` Menon, Nishanth
2009-03-17 6:16 ` dma_alloc_coherent fragmentation Menon, Nishanth
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=EAF47CD23C76F840A9E7FCE10091EFAB02B3D8F76F@dbde02.ent.ti.com \
--to=santosh.shilimkar@ti.com \
--cc=grgupta@ti.com \
--cc=linux-omap@vger.kernel.org \
--cc=nm@ti.com \
--cc=pramodforum@gmail.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;
as well as URLs for NNTP newsgroup(s).