On Thu 18-03-21 10:59:10, Oscar Salvador wrote:
> On Thu, Mar 18, 2021 at 10:29:57AM +0100, Michal Hocko wrote:
> > On Thu 18-03-21 09:54:01, Oscar Salvador wrote:
> > [...]
> > > @@ -2287,10 +2288,12 @@ static int alloc_and_dissolve_huge_page(struct
> > > hstate *h, struct page *old_page)
> > >
On Thu, Mar 18, 2021 at 10:29:57AM +0100, Michal Hocko wrote:
> On Thu 18-03-21 09:54:01, Oscar Salvador wrote:
> [...]
> > @@ -2287,10 +2288,12 @@ static int alloc_and_dissolve_huge_page(struct
> > hstate *h, struct page *old_page)
> > goto unlock;
> > } else if
On Thu 18-03-21 09:54:01, Oscar Salvador wrote:
[...]
> @@ -2287,10 +2288,12 @@ static int alloc_and_dissolve_huge_page(struct hstate
> *h, struct page *old_page)
> goto unlock;
> } else if (page_count(old_page)) {
> /*
> - * Someone has grabbed the
On Wed, Mar 17, 2021 at 03:26:50PM +0100, Michal Hocko wrote:
> it would be imho better to retry inside alloc_and_dissolve_huge_page
> because it already has its retry logic implemented.
>
> But not something I will insist on.
Ok, what about this (I did not even compile it yet, but gives a rough
On Wed 17-03-21 12:12:50, Oscar Salvador wrote:
> alloc_contig_range() will fail if it finds a HugeTLB page within the range,
> without a chance to handle them. Since HugeTLB pages can be migrated as any
> LRU or Movable page, it does not make sense to bail out without trying.
> Enable the
alloc_contig_range() will fail if it finds a HugeTLB page within the range,
without a chance to handle them. Since HugeTLB pages can be migrated as any
LRU or Movable page, it does not make sense to bail out without trying.
Enable the interface to recognize in-use HugeTLB pages so we can migrate
6 matches
Mail list logo
