Re: [PATCH 15/18] mm, hugetlb: move up anon_vma_prepare()

2013-07-31 Thread Naoya Horiguchi
On Wed, Jul 31, 2013 at 02:12:21PM +0900, Joonsoo Kim wrote: > On Mon, Jul 29, 2013 at 03:19:15PM -0400, Naoya Horiguchi wrote: > > On Mon, Jul 29, 2013 at 03:05:37PM -0400, Naoya Horiguchi wrote: > > > On Mon, Jul 29, 2013 at 02:32:06PM +0900, Joonsoo Kim wrote: > > > > If we fail with a

Re: [PATCH 15/18] mm, hugetlb: move up anon_vma_prepare()

2013-07-31 Thread Naoya Horiguchi
On Wed, Jul 31, 2013 at 02:12:21PM +0900, Joonsoo Kim wrote: On Mon, Jul 29, 2013 at 03:19:15PM -0400, Naoya Horiguchi wrote: On Mon, Jul 29, 2013 at 03:05:37PM -0400, Naoya Horiguchi wrote: On Mon, Jul 29, 2013 at 02:32:06PM +0900, Joonsoo Kim wrote: If we fail with a allocated

Re: [PATCH 15/18] mm, hugetlb: move up anon_vma_prepare()

2013-07-30 Thread Joonsoo Kim
On Mon, Jul 29, 2013 at 03:19:15PM -0400, Naoya Horiguchi wrote: > On Mon, Jul 29, 2013 at 03:05:37PM -0400, Naoya Horiguchi wrote: > > On Mon, Jul 29, 2013 at 02:32:06PM +0900, Joonsoo Kim wrote: > > > If we fail with a allocated hugepage, it is hard to recover properly. > > > One such example is

Re: [PATCH 15/18] mm, hugetlb: move up anon_vma_prepare()

2013-07-30 Thread Joonsoo Kim
On Mon, Jul 29, 2013 at 03:19:15PM -0400, Naoya Horiguchi wrote: On Mon, Jul 29, 2013 at 03:05:37PM -0400, Naoya Horiguchi wrote: On Mon, Jul 29, 2013 at 02:32:06PM +0900, Joonsoo Kim wrote: If we fail with a allocated hugepage, it is hard to recover properly. One such example is reserve

Re: [PATCH 15/18] mm, hugetlb: move up anon_vma_prepare()

2013-07-29 Thread Naoya Horiguchi
On Mon, Jul 29, 2013 at 03:05:37PM -0400, Naoya Horiguchi wrote: > On Mon, Jul 29, 2013 at 02:32:06PM +0900, Joonsoo Kim wrote: > > If we fail with a allocated hugepage, it is hard to recover properly. > > One such example is reserve count. We don't have any method to recover > > reserve count.

Re: [PATCH 15/18] mm, hugetlb: move up anon_vma_prepare()

2013-07-29 Thread Naoya Horiguchi
On Mon, Jul 29, 2013 at 02:32:06PM +0900, Joonsoo Kim wrote: > If we fail with a allocated hugepage, it is hard to recover properly. > One such example is reserve count. We don't have any method to recover > reserve count. Although, I will introduce a function to recover reserve > count in

Re: [PATCH 15/18] mm, hugetlb: move up anon_vma_prepare()

2013-07-29 Thread Naoya Horiguchi
On Mon, Jul 29, 2013 at 02:32:06PM +0900, Joonsoo Kim wrote: If we fail with a allocated hugepage, it is hard to recover properly. One such example is reserve count. We don't have any method to recover reserve count. Although, I will introduce a function to recover reserve count in following

Re: [PATCH 15/18] mm, hugetlb: move up anon_vma_prepare()

2013-07-29 Thread Naoya Horiguchi
On Mon, Jul 29, 2013 at 03:05:37PM -0400, Naoya Horiguchi wrote: On Mon, Jul 29, 2013 at 02:32:06PM +0900, Joonsoo Kim wrote: If we fail with a allocated hugepage, it is hard to recover properly. One such example is reserve count. We don't have any method to recover reserve count. Although,

[PATCH 15/18] mm, hugetlb: move up anon_vma_prepare()

2013-07-28 Thread Joonsoo Kim
If we fail with a allocated hugepage, it is hard to recover properly. One such example is reserve count. We don't have any method to recover reserve count. Although, I will introduce a function to recover reserve count in following patch, it is better not to allocate a hugepage as much as

[PATCH 15/18] mm, hugetlb: move up anon_vma_prepare()

2013-07-28 Thread Joonsoo Kim
If we fail with a allocated hugepage, it is hard to recover properly. One such example is reserve count. We don't have any method to recover reserve count. Although, I will introduce a function to recover reserve count in following patch, it is better not to allocate a hugepage as much as