Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1660719 > unrolled thread

[patch -mm] mm, hugetlb: schedule when potentially allocating many hugepages

Started byDavid Rientjes <rientjes@google.com>
First post2017-06-08 06:10 +0200
Last post2017-06-10 00:40 +0200
Articles 5 — 2 participants

Back to article view | Back to linux.kernel


Contents

  [patch -mm] mm, hugetlb: schedule when potentially allocating many  hugepages David Rientjes <rientjes@google.com> - 2017-06-08 06:10 +0200
    Re: [patch -mm] mm, hugetlb: schedule when potentially allocating  many hugepages Mike Kravetz <mike.kravetz@oracle.com> - 2017-06-08 06:40 +0200
      [patch v2 -mm] mm, hugetlb: schedule when potentially allocating  many hugepages David Rientjes <rientjes@google.com> - 2017-06-10 00:40 +0200
        Re: [patch v2 -mm] mm, hugetlb: schedule when potentially allocating  many hugepages Mike Kravetz <mike.kravetz@oracle.com> - 2017-06-10 00:50 +0200
      Re: [patch -mm] mm, hugetlb: schedule when potentially allocating  many hugepages David Rientjes <rientjes@google.com> - 2017-06-10 00:40 +0200

#1660719 — [patch -mm] mm, hugetlb: schedule when potentially allocating many hugepages

FromDavid Rientjes <rientjes@google.com>
Date2017-06-08 06:10 +0200
Subject[patch -mm] mm, hugetlb: schedule when potentially allocating many hugepages
Message-ID<tPWVI-7FJ-9@gated-at.bofh.it>
A few hugetlb allocators loop while calling the page allocator and can
potentially prevent rescheduling if the page allocator slowpath is not
utilized.

Conditionally schedule when large numbers of hugepages can be allocated.

Signed-off-by: David Rientjes <rientjes@google.com>
---
 Based on -mm only to prevent merge conflicts with
 "mm/hugetlb.c: warn the user when issues arise on boot due to hugepages"

 mm/hugetlb.c | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/mm/hugetlb.c b/mm/hugetlb.c
--- a/mm/hugetlb.c
+++ b/mm/hugetlb.c
@@ -1754,6 +1754,7 @@ static int gather_surplus_pages(struct hstate *h, int delta)
 			break;
 		}
 		list_add(&page->lru, &surplus_list);
+		cond_resched();
 	}
 	allocated += i;
 
@@ -2222,6 +2223,7 @@ static void __init hugetlb_hstate_alloc_pages(struct hstate *h)
 		} else if (!alloc_fresh_huge_page(h,
 					 &node_states[N_MEMORY]))
 			break;
+		cond_resched();
 	}
 	if (i < h->max_huge_pages) {
 		char buf[32];
@@ -2364,6 +2366,7 @@ static unsigned long set_max_huge_pages(struct hstate *h, unsigned long count,
 			ret = alloc_fresh_gigantic_page(h, nodes_allowed);
 		else
 			ret = alloc_fresh_huge_page(h, nodes_allowed);
+		cond_resched();
 		spin_lock(&hugetlb_lock);
 		if (!ret)
 			goto out;

[toc] | [next] | [standalone]


#1660731 — Re: [patch -mm] mm, hugetlb: schedule when potentially allocating many hugepages

FromMike Kravetz <mike.kravetz@oracle.com>
Date2017-06-08 06:40 +0200
SubjectRe: [patch -mm] mm, hugetlb: schedule when potentially allocating many hugepages
Message-ID<tPXoJ-7V3-5@gated-at.bofh.it>
In reply to#1660719
On 06/07/2017 09:03 PM, David Rientjes wrote:
> A few hugetlb allocators loop while calling the page allocator and can
> potentially prevent rescheduling if the page allocator slowpath is not
> utilized.
> 
> Conditionally schedule when large numbers of hugepages can be allocated.
> 
> Signed-off-by: David Rientjes <rientjes@google.com>
> ---
>  Based on -mm only to prevent merge conflicts with
>  "mm/hugetlb.c: warn the user when issues arise on boot due to hugepages"
> 
>  mm/hugetlb.c | 3 +++
>  1 file changed, 3 insertions(+)
> 
> diff --git a/mm/hugetlb.c b/mm/hugetlb.c
> --- a/mm/hugetlb.c
> +++ b/mm/hugetlb.c
> @@ -1754,6 +1754,7 @@ static int gather_surplus_pages(struct hstate *h, int delta)
>  			break;
>  		}
>  		list_add(&page->lru, &surplus_list);
> +		cond_resched();
>  	}
>  	allocated += i;
>  
> @@ -2222,6 +2223,7 @@ static void __init hugetlb_hstate_alloc_pages(struct hstate *h)
>  		} else if (!alloc_fresh_huge_page(h,
>  					 &node_states[N_MEMORY]))
>  			break;
> +		cond_resched();
>  	}
>  	if (i < h->max_huge_pages) {
>  		char buf[32];
> @@ -2364,6 +2366,7 @@ static unsigned long set_max_huge_pages(struct hstate *h, unsigned long count,
>  			ret = alloc_fresh_gigantic_page(h, nodes_allowed);
>  		else
>  			ret = alloc_fresh_huge_page(h, nodes_allowed);
> +		cond_resched();

Are not the following lines immediately before the above huge page allocation
in set_max_huge_pages, or am I looking at an incorrect version of the file?

		/* yield cpu to avoid soft lockup */
		cond_resched();

-- 
Mike Kravetz

>  		spin_lock(&hugetlb_lock);
>  		if (!ret)
>  			goto out;
> 
> --
> To unsubscribe, send a message with 'unsubscribe linux-mm' in
> the body to majordomo@kvack.org.  For more info on Linux MM,
> see: http://www.linux-mm.org/ .
> Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
> 

[toc] | [prev] | [next] | [standalone]


#1662787 — [patch v2 -mm] mm, hugetlb: schedule when potentially allocating many hugepages

FromDavid Rientjes <rientjes@google.com>
Date2017-06-10 00:40 +0200
Subject[patch v2 -mm] mm, hugetlb: schedule when potentially allocating many hugepages
Message-ID<tQAJr-7ia-3@gated-at.bofh.it>
In reply to#1660731
A few hugetlb allocators loop while calling the page allocator and can
potentially prevent rescheduling if the page allocator slowpath is not
utilized.

Conditionally schedule when large numbers of hugepages can be allocated.

Signed-off-by: David Rientjes <rientjes@google.com>
---
 Based on -mm only to prevent merge conflicts with
 "mm/hugetlb.c: warn the user when issues arise on boot due to hugepages"

 v2: removed redundant cond_resched() per Mike

 mm/hugetlb.c | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/mm/hugetlb.c b/mm/hugetlb.c
--- a/mm/hugetlb.c
+++ b/mm/hugetlb.c
@@ -1754,6 +1754,7 @@ static int gather_surplus_pages(struct hstate *h, int delta)
 			break;
 		}
 		list_add(&page->lru, &surplus_list);
+		cond_resched();
 	}
 	allocated += i;
 
@@ -2222,6 +2223,7 @@ static void __init hugetlb_hstate_alloc_pages(struct hstate *h)
 		} else if (!alloc_fresh_huge_page(h,
 					 &node_states[N_MEMORY]))
 			break;
+		cond_resched();
 	}
 	if (i < h->max_huge_pages) {
 		char buf[32];

[toc] | [prev] | [next] | [standalone]


#1662804 — Re: [patch v2 -mm] mm, hugetlb: schedule when potentially allocating many hugepages

FromMike Kravetz <mike.kravetz@oracle.com>
Date2017-06-10 00:50 +0200
SubjectRe: [patch v2 -mm] mm, hugetlb: schedule when potentially allocating many hugepages
Message-ID<tQAT8-7mJ-19@gated-at.bofh.it>
In reply to#1662787
On 06/09/2017 03:36 PM, David Rientjes wrote:
> A few hugetlb allocators loop while calling the page allocator and can
> potentially prevent rescheduling if the page allocator slowpath is not
> utilized.
> 
> Conditionally schedule when large numbers of hugepages can be allocated.
> 
> Signed-off-by: David Rientjes <rientjes@google.com>

Thanks for doing this.

Reviewed-by: Mike Kravetz <mike.kravetz@oracle.com>

-- 
Mike Kravetz

> ---
>  Based on -mm only to prevent merge conflicts with
>  "mm/hugetlb.c: warn the user when issues arise on boot due to hugepages"
> 
>  v2: removed redundant cond_resched() per Mike
> 
>  mm/hugetlb.c | 2 ++
>  1 file changed, 2 insertions(+)
> 
> diff --git a/mm/hugetlb.c b/mm/hugetlb.c
> --- a/mm/hugetlb.c
> +++ b/mm/hugetlb.c
> @@ -1754,6 +1754,7 @@ static int gather_surplus_pages(struct hstate *h, int delta)
>  			break;
>  		}
>  		list_add(&page->lru, &surplus_list);
> +		cond_resched();
>  	}
>  	allocated += i;
>  
> @@ -2222,6 +2223,7 @@ static void __init hugetlb_hstate_alloc_pages(struct hstate *h)
>  		} else if (!alloc_fresh_huge_page(h,
>  					 &node_states[N_MEMORY]))
>  			break;
> +		cond_resched();
>  	}
>  	if (i < h->max_huge_pages) {
>  		char buf[32];
> 
> --
> To unsubscribe, send a message with 'unsubscribe linux-mm' in
> the body to majordomo@kvack.org.  For more info on Linux MM,
> see: http://www.linux-mm.org/ .
> Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
> 

[toc] | [prev] | [next] | [standalone]


#1662791 — Re: [patch -mm] mm, hugetlb: schedule when potentially allocating many hugepages

FromDavid Rientjes <rientjes@google.com>
Date2017-06-10 00:40 +0200
SubjectRe: [patch -mm] mm, hugetlb: schedule when potentially allocating many hugepages
Message-ID<tQAJr-7ia-5@gated-at.bofh.it>
In reply to#1660731
On Wed, 7 Jun 2017, Mike Kravetz wrote:

> > @@ -2364,6 +2366,7 @@ static unsigned long set_max_huge_pages(struct hstate *h, unsigned long count,
> >  			ret = alloc_fresh_gigantic_page(h, nodes_allowed);
> >  		else
> >  			ret = alloc_fresh_huge_page(h, nodes_allowed);
> > +		cond_resched();
> 
> Are not the following lines immediately before the above huge page allocation
> in set_max_huge_pages, or am I looking at an incorrect version of the file?
> 
> 		/* yield cpu to avoid soft lockup */
> 		cond_resched();

Ahh, we don't have this in our tree, thanks for catching it.  The other 
two cond_resched()'s are needed because we have reproduced them, so I'll 
send a v2.

[toc] | [prev] | [standalone]


Back to top | Article view | linux.kernel


csiph-web