From: Michal Hocko <mhocko@kernel.org>
To: Roman Gushchin <guro@fb.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Aslan Bakirov <aslan@fb.com>,
linux-mm@kvack.org, kernel-team@fb.com,
linux-kernel@vger.kernel.org, Rik van Riel <riel@surriel.com>,
Mike Kravetz <mike.kravetz@oracle.com>,
Andreas Schaufler <andreas.schaufler@gmx.de>,
Randy Dunlap <rdunlap@infradead.org>,
Joonsoo Kim <js1304@gmail.com>
Subject: Re: [PATCH v4 2/2] mm: hugetlb: optionally allocate gigantic hugepages using cma
Date: Tue, 7 Apr 2020 09:03:31 +0200 [thread overview]
Message-ID: <20200407070331.GD18914@dhcp22.suse.cz> (raw)
In-Reply-To: <20200407010431.1286488-3-guro@fb.com>
On Mon 06-04-20 18:04:31, Roman Gushchin wrote:
[...]
My ack still applies but I have only noticed two minor things now.
[...]
> @@ -1281,8 +1308,14 @@ static void update_and_free_page(struct hstate *h, struct page *page)
> set_compound_page_dtor(page, NULL_COMPOUND_DTOR);
> set_page_refcounted(page);
> if (hstate_is_gigantic(h)) {
> + /*
> + * Temporarily drop the hugetlb_lock, because
> + * we might block in free_gigantic_page().
> + */
> + spin_unlock(&hugetlb_lock);
> destroy_compound_gigantic_page(page, huge_page_order(h));
> free_gigantic_page(page, huge_page_order(h));
> + spin_lock(&hugetlb_lock);
This is OK with the current code because existing paths do not have to
revalidate the state AFAICS but it is a bit subtle. I have checked the
cma_free path and it can only sleep on the cma->lock unless I am missing
something. This lock is only used for cma bitmap manipulation and the
mutex sounds like an overkill there and it can be replaced by a
spinlock.
Sounds like a follow up patch material to me.
[...]
> + for_each_node_state(nid, N_ONLINE) {
> + int res;
> +
> + size = min(per_node, hugetlb_cma_size - reserved);
> + size = round_up(size, PAGE_SIZE << order);
> +
> + res = cma_declare_contiguous_nid(0, size, 0, PAGE_SIZE << order,
> + 0, false, "hugetlb",
> + &hugetlb_cma[nid], nid);
> + if (res) {
> + pr_warn("hugetlb_cma: reservation failed: err %d, node %d",
> + res, nid);
> + break;
Do we really have to break out after a single node failure? There might
be other nodes that can satisfy the allocation. You are not cleaning up
previous allocations so there is a partial state and then it would make
more sense to me to simply s@break@continue@ here.
> + }
> +
> + reserved += size;
> + pr_info("hugetlb_cma: reserved %lu MiB on node %d\n",
> + size / SZ_1M, nid);
> +
> + if (reserved >= hugetlb_cma_size)
> + break;
> + }
> +}
--
Michal Hocko
SUSE Labs
next prev parent reply other threads:[~2020-04-07 7:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-07 1:04 [PATCH v4 0/2] mm: using CMA for 1 GB hugepages allocation Roman Gushchin
2020-04-07 1:04 ` [PATCH v4 1/2] mm: cma: NUMA node interface Roman Gushchin
2020-04-07 1:04 ` [PATCH v4 2/2] mm: hugetlb: optionally allocate gigantic hugepages using cma Roman Gushchin
2020-04-07 7:03 ` Michal Hocko [this message]
2020-04-07 15:25 ` Roman Gushchin
2020-04-07 15:40 ` Michal Hocko
2020-04-07 16:06 ` Roman Gushchin
2020-04-07 16:23 ` Michal Hocko
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=20200407070331.GD18914@dhcp22.suse.cz \
--to=mhocko@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=andreas.schaufler@gmx.de \
--cc=aslan@fb.com \
--cc=guro@fb.com \
--cc=js1304@gmail.com \
--cc=kernel-team@fb.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mike.kravetz@oracle.com \
--cc=rdunlap@infradead.org \
--cc=riel@surriel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.