2015-03-17 18:46 GMT+09:00 Aneesh Kumar K.V :
> Joonsoo Kim writes:
>
>> I passed boot test on x86, ARM32 and ARM64. I did some stress tests
>> on x86 and there is no problem. Feel free to enjoy and please give me
>> a feedback. :)
>
> Tested on ppc64 with kvm. (I used the
2015-03-17 18:46 GMT+09:00 Aneesh Kumar K.V aneesh.ku...@linux.vnet.ibm.com:
Joonsoo Kim iamjoonsoo@lge.com writes:
I passed boot test on x86, ARM32 and ARM64. I did some stress tests
on x86 and there is no problem. Feel free to enjoy and please give me
a feedback. :)
Tested on ppc64
Joonsoo Kim writes:
> I passed boot test on x86, ARM32 and ARM64. I did some stress tests
> on x86 and there is no problem. Feel free to enjoy and please give me
> a feedback. :)
Tested on ppc64 with kvm. (I used the CONFIG_SPARSEMEM_VMEMMAP). I will
check with other sparsemem config and update
Joonsoo Kim iamjoonsoo@lge.com writes:
I passed boot test on x86, ARM32 and ARM64. I did some stress tests
on x86 and there is no problem. Feel free to enjoy and please give me
a feedback. :)
Tested on ppc64 with kvm. (I used the CONFIG_SPARSEMEM_VMEMMAP). I will
check with other
On Thu, Mar 05, 2015 at 06:48:50PM +0100, Vlastimil Babka wrote:
> On 03/05/2015 05:53 PM, Vlastimil Babka wrote:
> > On 02/12/2015 08:32 AM, Joonsoo Kim wrote:
> >>
> >> 1) Break non-overlapped zone assumption
> >> CMA regions could be spread to all memory range, so, to keep all of them
> >>
On 03/05/2015 05:53 PM, Vlastimil Babka wrote:
> On 02/12/2015 08:32 AM, Joonsoo Kim wrote:
>>
>> 1) Break non-overlapped zone assumption
>> CMA regions could be spread to all memory range, so, to keep all of them
>> into one zone, span of ZONE_CMA would be overlap to other zones'.
>
> From
On 02/12/2015 08:32 AM, Joonsoo Kim wrote:
>
> 1) Break non-overlapped zone assumption
> CMA regions could be spread to all memory range, so, to keep all of them
> into one zone, span of ZONE_CMA would be overlap to other zones'.
>From patch 13/16 ut seems to me that indeed the ZONE_CMA spans
On 02/12/2015 08:32 AM, Joonsoo Kim wrote:
1) Break non-overlapped zone assumption
CMA regions could be spread to all memory range, so, to keep all of them
into one zone, span of ZONE_CMA would be overlap to other zones'.
From patch 13/16 ut seems to me that indeed the ZONE_CMA spans the
On 03/05/2015 05:53 PM, Vlastimil Babka wrote:
On 02/12/2015 08:32 AM, Joonsoo Kim wrote:
1) Break non-overlapped zone assumption
CMA regions could be spread to all memory range, so, to keep all of them
into one zone, span of ZONE_CMA would be overlap to other zones'.
From patch 13/16 ut
On Thu, Mar 05, 2015 at 06:48:50PM +0100, Vlastimil Babka wrote:
On 03/05/2015 05:53 PM, Vlastimil Babka wrote:
On 02/12/2015 08:32 AM, Joonsoo Kim wrote:
1) Break non-overlapped zone assumption
CMA regions could be spread to all memory range, so, to keep all of them
into one zone,
Hello,
This series try to solve problems of current CMA implementation.
CMA is introduced to provide physically contiguous pages at runtime
without exclusive reserved memory area. But, current implementation
works like as previous reserved memory approach, because freepages
on CMA region are
Hello,
This series try to solve problems of current CMA implementation.
CMA is introduced to provide physically contiguous pages at runtime
without exclusive reserved memory area. But, current implementation
works like as previous reserved memory approach, because freepages
on CMA region are
12 matches
Mail list logo
