Re: [PATCH 4/9] mm, hugetlb: fix and clean-up node iteration code to alloc or free

2013-07-18 Thread Joonsoo Kim
On Wed, Jul 17, 2013 at 10:00:48AM +0800, Jianguo Wu wrote: > On 2013/7/15 17:52, Joonsoo Kim wrote: > > > Current node iteration code have a minor problem which do one more > > node rotation if we can't succeed to allocate. For example, > > if we start to allocate at node 0, we stop to iterate

Re: [PATCH 4/9] mm, hugetlb: fix and clean-up node iteration code to alloc or free

2013-07-18 Thread Joonsoo Kim
On Wed, Jul 17, 2013 at 10:00:48AM +0800, Jianguo Wu wrote: On 2013/7/15 17:52, Joonsoo Kim wrote: Current node iteration code have a minor problem which do one more node rotation if we can't succeed to allocate. For example, if we start to allocate at node 0, we stop to iterate at node

Re: [PATCH 4/9] mm, hugetlb: fix and clean-up node iteration code to alloc or free

2013-07-16 Thread Jianguo Wu
On 2013/7/15 17:52, Joonsoo Kim wrote: > Current node iteration code have a minor problem which do one more > node rotation if we can't succeed to allocate. For example, > if we start to allocate at node 0, we stop to iterate at node 0. > Then we start to allocate at node 1 for next allocation. >

Re: [PATCH 4/9] mm, hugetlb: fix and clean-up node iteration code to alloc or free

2013-07-16 Thread Jianguo Wu
On 2013/7/15 17:52, Joonsoo Kim wrote: Current node iteration code have a minor problem which do one more node rotation if we can't succeed to allocate. For example, if we start to allocate at node 0, we stop to iterate at node 0. Then we start to allocate at node 1 for next allocation. I

Re: [PATCH 4/9] mm, hugetlb: fix and clean-up node iteration code to alloc or free

2013-07-15 Thread Joonsoo Kim
On Mon, Jul 15, 2013 at 07:57:37PM +0530, Aneesh Kumar K.V wrote: > Joonsoo Kim writes: > > > Current node iteration code have a minor problem which do one more > > node rotation if we can't succeed to allocate. For example, > > if we start to allocate at node 0, we stop to iterate at node 0. >

Re: [PATCH 4/9] mm, hugetlb: fix and clean-up node iteration code to alloc or free

2013-07-15 Thread Aneesh Kumar K.V
Joonsoo Kim writes: > Current node iteration code have a minor problem which do one more > node rotation if we can't succeed to allocate. For example, > if we start to allocate at node 0, we stop to iterate at node 0. > Then we start to allocate at node 1 for next allocation. Can you explain

[PATCH 4/9] mm, hugetlb: fix and clean-up node iteration code to alloc or free

2013-07-15 Thread Joonsoo Kim
Current node iteration code have a minor problem which do one more node rotation if we can't succeed to allocate. For example, if we start to allocate at node 0, we stop to iterate at node 0. Then we start to allocate at node 1 for next allocation. I introduce new macros

[PATCH 4/9] mm, hugetlb: fix and clean-up node iteration code to alloc or free

2013-07-15 Thread Joonsoo Kim
Current node iteration code have a minor problem which do one more node rotation if we can't succeed to allocate. For example, if we start to allocate at node 0, we stop to iterate at node 0. Then we start to allocate at node 1 for next allocation. I introduce new macros

Re: [PATCH 4/9] mm, hugetlb: fix and clean-up node iteration code to alloc or free

2013-07-15 Thread Aneesh Kumar K.V
Joonsoo Kim iamjoonsoo@lge.com writes: Current node iteration code have a minor problem which do one more node rotation if we can't succeed to allocate. For example, if we start to allocate at node 0, we stop to iterate at node 0. Then we start to allocate at node 1 for next allocation.

Re: [PATCH 4/9] mm, hugetlb: fix and clean-up node iteration code to alloc or free

2013-07-15 Thread Joonsoo Kim
On Mon, Jul 15, 2013 at 07:57:37PM +0530, Aneesh Kumar K.V wrote: Joonsoo Kim iamjoonsoo@lge.com writes: Current node iteration code have a minor problem which do one more node rotation if we can't succeed to allocate. For example, if we start to allocate at node 0, we stop to iterate