From: Mike Kravetz <mike.kravetz@oracle.com>
To: Wei Yang <richard.weiyang@linux.alibaba.com>, akpm@linux-foundation.org
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org, bhe@redhat.com
Subject: Re: [Patch v3 7/7] mm/hugetlb: take the free hpage during the iteration directly
Date: Mon, 31 Aug 2020 16:06:54 -0700 [thread overview]
Message-ID: <d36e57db-b02f-fd75-6c0c-734635f58ff5@oracle.com> (raw)
In-Reply-To: <20200831022351.20916-8-richard.weiyang@linux.alibaba.com>
On 8/30/20 7:23 PM, Wei Yang wrote:
> Function dequeue_huge_page_node_exact() iterates the free list and
> return the first valid free hpage.
>
> Instead of break and check the loop variant, we could return in the loop
> directly. This could reduce some redundant check.
>
> Signed-off-by: Wei Yang <richard.weiyang@linux.alibaba.com>
> ---
> mm/hugetlb.c | 20 ++++++++------------
> 1 file changed, 8 insertions(+), 12 deletions(-)
>
> diff --git a/mm/hugetlb.c b/mm/hugetlb.c
> index 7b3357c1dcec..709be7ab65af 100644
> --- a/mm/hugetlb.c
> +++ b/mm/hugetlb.c
> @@ -1040,21 +1040,17 @@ static struct page *dequeue_huge_page_node_exact(struct hstate *h, int nid)
> if (nocma && is_migrate_cma_page(page))
> continue;
>
> - if (!PageHWPoison(page))
> + if (PageHWPoison(page))
> break;
Previously, when encountering a PageHWPoison(page) the loop would continue
and check the next page in the list. It now breaks the loop and returns
NULL. Is not this a change in behavior? Perhaps you want to change that
break to a continue. Or, restructure in some other way.
--
Mike Kravetz
> +
> + list_move(&page->lru, &h->hugepage_activelist);
> + set_page_refcounted(page);
> + h->free_huge_pages--;
> + h->free_huge_pages_node[nid]--;
> + return page;
> }
>
> - /*
> - * if 'non-isolated free hugepage' not found on the list,
> - * the allocation fails.
> - */
> - if (&h->hugepage_freelists[nid] == &page->lru)
> - return NULL;
> - list_move(&page->lru, &h->hugepage_activelist);
> - set_page_refcounted(page);
> - h->free_huge_pages--;
> - h->free_huge_pages_node[nid]--;
> - return page;
> + return NULL;
> }
>
> static struct page *dequeue_huge_page_nodemask(struct hstate *h, gfp_t gfp_mask, int nid,
>
next prev parent reply other threads:[~2020-08-31 23:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-31 2:23 [Patch v3 0/7] mm/hugetlb: code refine and simplification Wei Yang
2020-08-31 2:23 ` [Patch v3 1/7] mm/hugetlb: not necessary to coalesce regions recursively Wei Yang
2020-08-31 2:23 ` [Patch v3 2/7] mm/hugetlb: remove VM_BUG_ON(!nrg) in get_file_region_entry_from_cache() Wei Yang
2020-08-31 2:23 ` [Patch v3 3/7] mm/hugetlb: use list_splice to merge two list at once Wei Yang
2020-08-31 2:23 ` [Patch v3 4/7] mm/hugetlb: count file_region to be added when regions_needed != NULL Wei Yang
2020-08-31 2:23 ` [Patch v3 5/7] mm/hugetlb: a page from buddy is not on any list Wei Yang
2020-08-31 2:23 ` [Patch v3 6/7] mm/hugetlb: narrow the hugetlb_lock protection area during preparing huge page Wei Yang
2020-08-31 2:23 ` [Patch v3 7/7] mm/hugetlb: take the free hpage during the iteration directly Wei Yang
2020-08-31 23:06 ` Mike Kravetz [this message]
2020-09-01 1:42 ` Wei Yang
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=d36e57db-b02f-fd75-6c0c-734635f58ff5@oracle.com \
--to=mike.kravetz@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=bhe@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=richard.weiyang@linux.alibaba.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox