2012/2/5 Michal Nazarewicz min...@mina86.com:
On Sun, 05 Feb 2012 05:25:40 +0100, Hillf Danton dhi...@gmail.com wrote:
Without boot mem reservation, what is the successful rate of CMA to
serve requests of 1MiB, 2MiB, 4MiB and 8MiB chunks?
CMA will work as long as you manage to get some
On Fri, Feb 3, 2012 at 8:18 PM, Marek Szyprowski
m.szyprow...@samsung.com wrote:
The Contiguous Memory Allocator is a set of helper functions for DMA
mapping framework that improves allocations of contiguous memory chunks.
CMA grabs memory on system boot, marks it with CMA_MIGRATE_TYPE and
The Contiguous Memory Allocator is a set of helper functions for DMA
mapping framework that improves allocations of contiguous memory chunks.
CMA grabs memory on system boot, marks it with CMA_MIGRATE_TYPE and
gives back to the system. Kernel is allowed to allocate movable pages
within CMA's
Hi Marek,
On Mon, Jan 30, 2012 at 9:43 AM, Marek Szyprowski
m.szyprow...@samsung.com wrote:
Did you managed to fix this issue?
Yes -- the recent increase in the vmalloc region triggered a bigger
truncation in the system RAM than we had before, and therefore
conflicted with the previous
Hello,
On Saturday, January 28, 2012 7:57 PM Ohad Ben-Cohen wrote:
On Fri, Jan 27, 2012 at 5:17 PM, Marek Szyprowski
m.szyprow...@samsung.com wrote:
There have been some vmalloc layout changes merged to v3.3-rc1.
That was dead-on, thanks a lot!
Did you managed to fix this issue?
I
Hi Marek,
On Fri, Jan 27, 2012 at 5:17 PM, Marek Szyprowski
m.szyprow...@samsung.com wrote:
There have been some vmalloc layout changes merged to v3.3-rc1.
That was dead-on, thanks a lot!
I did then bump into a different allocation failure which happened
because dma_alloc_from_contiguous()
Hi Marek,
With v19, I can't seem to allocate big regions anymore (e.g. 101MiB).
In particular, this seems to fail:
On Thu, Jan 26, 2012 at 11:00 AM, Marek Szyprowski
m.szyprow...@samsung.com wrote:
+static int cma_activate_area(unsigned long base_pfn, unsigned long count)
+{
+ unsigned
Hi Ohad,
On Friday, January 27, 2012 10:44 AM Ohad Ben-Cohen wrote:
With v19, I can't seem to allocate big regions anymore (e.g. 101MiB).
In particular, this seems to fail:
On Thu, Jan 26, 2012 at 11:00 AM, Marek Szyprowski
m.szyprow...@samsung.com wrote:
+static int
2012/1/27 Marek Szyprowski m.szyprow...@samsung.com:
Hi Ohad,
On Friday, January 27, 2012 10:44 AM Ohad Ben-Cohen wrote:
With v19, I can't seem to allocate big regions anymore (e.g. 101MiB).
In particular, this seems to fail:
On Thu, Jan 26, 2012 at 11:00 AM, Marek Szyprowski
Hello,
On Friday, January 27, 2012 3:28 PM Clark, Rob wrote:
2012/1/27 Marek Szyprowski m.szyprow...@samsung.com:
Hi Ohad,
On Friday, January 27, 2012 10:44 AM Ohad Ben-Cohen wrote:
With v19, I can't seem to allocate big regions anymore (e.g. 101MiB).
In particular, this seems to
2012/1/27 Marek Szyprowski m.szyprow...@samsung.com:
I've tested it with 256MiB on Exynos4 platform. Could you check if the
problem also appears on 3.2-cma-v19 branch (I've uploaded it a few hours
ago)
Exactly what I needed, thanks :)
Both v18 and v19 seem to work fine with 3.2.
The above
2012/1/27 Marek Szyprowski m.szyprow...@samsung.com:
Ohad, could you tell a bit more about your issue?
Sure, feel free to ask.
Does this 'large region'
is a device private region (declared with dma_declare_contiguous())
Yes, it is.
See omap_rproc_reserve_cma() in:
Hello,
On Friday, January 27, 2012 3:59 PM Ohad Ben-Cohen wrote:
2012/1/27 Marek Szyprowski m.szyprow...@samsung.com:
Ohad, could you tell a bit more about your issue?
Sure, feel free to ask.
Does this 'large region'
is a device private region (declared with dma_declare_contiguous())
The Contiguous Memory Allocator is a set of helper functions for DMA
mapping framework that improves allocations of contiguous memory chunks.
CMA grabs memory on system boot, marks it with CMA_MIGRATE_TYPE and
gives back to the system. Kernel is allowed to allocate movable pages
within CMA's
14 matches
Mail list logo
