From: Roman Gushchin <guro@fb.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Zi Yan <ziy@nvidia.com>, Joonsoo Kim <iamjoonsoo.kim@lge.com>,
Mike Kravetz <mike.kravetz@oracle.com>,
<saberlily.xia@hisilicon.com>, <linux-kernel@vger.kernel.org>,
<linux-mm@kvack.org>, <kernel-team@fb.com>,
Roman Gushchin <guro@fb.com>
Subject: [PATCH v1 0/2] mm: cma: introduce a non-blocking version of cma_release()
Date: Thu, 22 Oct 2020 15:53:06 -0700 [thread overview]
Message-ID: <20201022225308.2927890-1-guro@fb.com> (raw)
This small patchset introduces a non-blocking version of cma_release()
and simplifies the code in hugetlbfs, where previously we had to
temporarily drop hugetlb_lock around the cma_release() call.
It should help Zi Yan on his work on 1 GB THPs: splitting a gigantic
THP under a memory pressure requires a cma_release() call. If it's
a blocking function, it complicates the already complicated code.
Because there are at least two use cases like this (hugetlbfs is
another example), I believe it's just better to make cma_release()
non-blocking.
v1:
- introduce cma_release_nowait() instead of making cma_release()
non-blocking, for performance reasons
rfc:
https://lkml.org/lkml/2020/10/16/1050
Roman Gushchin (2):
mm: cma: introduce cma_release_nowait()
mm: hugetlb: don't drop hugetlb_lock around cma_release() call
include/linux/cma.h | 2 +
mm/cma.c | 93 +++++++++++++++++++++++++++++++++++++++++++++
mm/cma.h | 5 +++
mm/hugetlb.c | 11 ++----
4 files changed, 103 insertions(+), 8 deletions(-)
--
2.26.2
next reply other threads:[~2020-10-22 22:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-22 22:53 Roman Gushchin [this message]
2020-10-22 22:53 ` [PATCH v1 1/2] mm: cma: introduce cma_release_nowait() Roman Gushchin
2020-10-24 7:59 ` Christoph Hellwig
2020-10-27 19:56 ` Roman Gushchin
2020-10-22 22:53 ` [PATCH v1 2/2] mm: hugetlb: don't drop hugetlb_lock around cma_release() call Roman Gushchin
2020-10-22 23:42 ` [PATCH v1 0/2] mm: cma: introduce a non-blocking version of cma_release() Zi Yan
2020-10-23 0:47 ` Roman Gushchin
2020-10-23 0:58 ` Zi Yan
2020-10-23 20:55 ` Roman Gushchin
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=20201022225308.2927890-1-guro@fb.com \
--to=guro@fb.com \
--cc=akpm@linux-foundation.org \
--cc=iamjoonsoo.kim@lge.com \
--cc=kernel-team@fb.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mike.kravetz@oracle.com \
--cc=saberlily.xia@hisilicon.com \
--cc=ziy@nvidia.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;
as well as URLs for NNTP newsgroup(s).