From: Mike Kravetz <mike.kravetz@oracle.com>
To: Miaohe Lin <linmiaohe@huawei.com>, akpm@linux-foundation.org
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mm/hugetlb: optimize the surplus state transfer code in move_hugetlb_state()
Date: Fri, 12 Feb 2021 16:51:40 -0800 [thread overview]
Message-ID: <f3f61091-3a3f-5c6f-bcc3-934cac25a8e1@oracle.com> (raw)
In-Reply-To: <20210210071251.44084-1-linmiaohe@huawei.com>
On 2/9/21 11:12 PM, Miaohe Lin wrote:
> We should not transfer the per-node surplus state when we do not cross the
> node in order to save some cpu cycles
>
> Signed-off-by: Miaohe Lin <linmiaohe@huawei.com>
> ---
> mm/hugetlb.c | 6 ++++++
> 1 file changed, 6 insertions(+)
Thanks,
I was going to comment that the usual case is migrating to another node
and old_nid != new_nid. However, this really is workload and system
configuration dependent. In any case, the quick check is worth potentially
saving a lock/unlock cycle.
Reviewed-by: Mike Kravetz <mike.kravetz@oracle.com>
--
Mike Kravetz
>
> diff --git a/mm/hugetlb.c b/mm/hugetlb.c
> index da347047ea10..4f2c92ddbca4 100644
> --- a/mm/hugetlb.c
> +++ b/mm/hugetlb.c
> @@ -5632,6 +5632,12 @@ void move_hugetlb_state(struct page *oldpage, struct page *newpage, int reason)
> SetHPageTemporary(oldpage);
> ClearHPageTemporary(newpage);
>
> + /*
> + * There is no need to transfer the per-node surplus state
> + * when we do not cross the node.
> + */
> + if (new_nid == old_nid)
> + return;
> spin_lock(&hugetlb_lock);
> if (h->surplus_huge_pages_node[old_nid]) {
> h->surplus_huge_pages_node[old_nid]--;
>
prev parent reply other threads:[~2021-02-13 0:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-10 7:12 Miaohe Lin
2021-02-13 0:51 ` Mike Kravetz [this message]
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=f3f61091-3a3f-5c6f-bcc3-934cac25a8e1@oracle.com \
--to=mike.kravetz@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=linmiaohe@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
/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