>>
>> This is (yet another) update of CMA patches.
>
>
> How well CMA is supposed to work if you have mlocked processes? I've
> been testing these patches, and noticed that by creating a small mlocked
> process you start to get plenty of test_pages_isolated() failure warnings,
> and bigger allocati
> +static int __reclaim_pages(struct zone *zone, gfp_t gfp_mask, int count)
> +{
> + /*
> + * Increase level of watermarks to force kswapd do his job
> + * to stabilise at new watermark level.
> + */
> + __update_cma_watermarks(zone, count);
> +
> + /* Obey wa
2012/2/8 Michal Nazarewicz :
> On Wed, 08 Feb 2012 03:04:18 +0100, sandeep patil
> wrote:
>>
>> There's another problem I am facing with zone watermarks and CMA.
>>
>> Test details:
>> Memory : 480 MB of total memory, 128 MB CMA region
>> Test case
On Fri, Feb 3, 2012 at 6:04 AM, Mel Gorman wrote:
> On Fri, Feb 03, 2012 at 01:18:54PM +0100, Marek Szyprowski wrote:
>
> Nothing prevents two or more processes updating the wmarks at the same
> time which is racy and unpredictable. Today it is not much of a problem
> but CMA makes this path hotte
> Yeah, we are wondering ourselves about that. Could you try cherry-picking
> commit ad10eb079c97e27b4d27bc755c605226ce1625de (update migrate type on pcp
> when isolating) from git://github.com/mina86/linux-2.6.git? It probably
> won't
> apply cleanly but resolving the conflicts should not be har
Marek,
I am running a CMA test where I keep allocating from a CMA region as long
as the allocation fails due to lack of space.
However, I am seeing failures much before I expect them to happen.
When the allocation fails, I see a warning coming from __alloc_contig_range(),
because test_pages_isola
2011/11/18 Michal Nazarewicz :
> On Fri, 18 Nov 2011 22:20:48 +0100, sandeep patil
> wrote:
>>
>> I am running a simple test to allocate contiguous regions and write a log
>> on
>> in a file on sdcard simultaneously. I can reproduce this migration failure
>&
On Fri, Nov 18, 2011 at 8:43 AM, Marek Szyprowski
wrote:
> Welcome everyone once again,
> Please notice that this patch series is aimed to start further
> discussion. There are still few issues that need to be resolved before
> CMA will be really ready. The most hot problem is the issue with mova
