Re: [PATCH v2 07/20] mm, hugetlb: unify region structure handling

2013-08-22 Thread Joonsoo Kim
On Wed, Aug 21, 2013 at 03:27:38PM +0530, Aneesh Kumar K.V wrote: > Joonsoo Kim writes: > > > Currently, to track a reserved and allocated region, we use two different > > ways for MAP_SHARED and MAP_PRIVATE. For MAP_SHARED, we use > > address_mapping's private_list and, for MAP_PRIVATE, we use

Re: [PATCH v2 07/20] mm, hugetlb: unify region structure handling

2013-08-22 Thread Joonsoo Kim
On Wed, Aug 21, 2013 at 03:52:57PM +0530, Aneesh Kumar K.V wrote: > Joonsoo Kim writes: > > > Currently, to track a reserved and allocated region, we use two different > > ways for MAP_SHARED and MAP_PRIVATE. For MAP_SHARED, we use > > address_mapping's private_list and, for MAP_PRIVATE, we use

Re: [PATCH v2 07/20] mm, hugetlb: unify region structure handling

2013-08-22 Thread Joonsoo Kim
On Wed, Aug 21, 2013 at 03:52:57PM +0530, Aneesh Kumar K.V wrote: Joonsoo Kim iamjoonsoo@lge.com writes: Currently, to track a reserved and allocated region, we use two different ways for MAP_SHARED and MAP_PRIVATE. For MAP_SHARED, we use address_mapping's private_list and, for

Re: [PATCH v2 07/20] mm, hugetlb: unify region structure handling

2013-08-22 Thread Joonsoo Kim
On Wed, Aug 21, 2013 at 03:27:38PM +0530, Aneesh Kumar K.V wrote: Joonsoo Kim iamjoonsoo@lge.com writes: Currently, to track a reserved and allocated region, we use two different ways for MAP_SHARED and MAP_PRIVATE. For MAP_SHARED, we use address_mapping's private_list and, for

Re: [PATCH v2 07/20] mm, hugetlb: unify region structure handling

2013-08-21 Thread Aneesh Kumar K.V
Joonsoo Kim writes: > Currently, to track a reserved and allocated region, we use two different > ways for MAP_SHARED and MAP_PRIVATE. For MAP_SHARED, we use > address_mapping's private_list and, for MAP_PRIVATE, we use a resv_map. > Now, we are preparing to change a coarse grained lock which

Re: [PATCH v2 07/20] mm, hugetlb: unify region structure handling

2013-08-21 Thread Aneesh Kumar K.V
Joonsoo Kim writes: > Currently, to track a reserved and allocated region, we use two different > ways for MAP_SHARED and MAP_PRIVATE. For MAP_SHARED, we use > address_mapping's private_list and, for MAP_PRIVATE, we use a resv_map. > Now, we are preparing to change a coarse grained lock which

Re: [PATCH v2 07/20] mm, hugetlb: unify region structure handling

2013-08-21 Thread Aneesh Kumar K.V
Joonsoo Kim iamjoonsoo@lge.com writes: Currently, to track a reserved and allocated region, we use two different ways for MAP_SHARED and MAP_PRIVATE. For MAP_SHARED, we use address_mapping's private_list and, for MAP_PRIVATE, we use a resv_map. Now, we are preparing to change a coarse

Re: [PATCH v2 07/20] mm, hugetlb: unify region structure handling

2013-08-21 Thread Aneesh Kumar K.V
Joonsoo Kim iamjoonsoo@lge.com writes: Currently, to track a reserved and allocated region, we use two different ways for MAP_SHARED and MAP_PRIVATE. For MAP_SHARED, we use address_mapping's private_list and, for MAP_PRIVATE, we use a resv_map. Now, we are preparing to change a coarse

[PATCH v2 07/20] mm, hugetlb: unify region structure handling

2013-08-09 Thread Joonsoo Kim
Currently, to track a reserved and allocated region, we use two different ways for MAP_SHARED and MAP_PRIVATE. For MAP_SHARED, we use address_mapping's private_list and, for MAP_PRIVATE, we use a resv_map. Now, we are preparing to change a coarse grained lock which protect a region structure to

[PATCH v2 07/20] mm, hugetlb: unify region structure handling

2013-08-09 Thread Joonsoo Kim
Currently, to track a reserved and allocated region, we use two different ways for MAP_SHARED and MAP_PRIVATE. For MAP_SHARED, we use address_mapping's private_list and, for MAP_PRIVATE, we use a resv_map. Now, we are preparing to change a coarse grained lock which protect a region structure to