From: David Hildenbrand <david@redhat.com>
To: buddy.zhang@aliyun.com, akpm@linux-foundation.org
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mm/cma.c: find a named CMA area by name
Date: Tue, 14 Jan 2020 10:02:25 +0100 [thread overview]
Message-ID: <3cb5e071-c5c0-47f8-96e9-526ca5dbfc62@redhat.com> (raw)
In-Reply-To: <20200114075147.30672-1-buddy.zhang@aliyun.com>
On 14.01.20 08:51, buddy.zhang@aliyun.com wrote:
> From: BuddyZhang <buddy.zhang@aliyun.com>
>
> This function could help developer who want to find a special
> named CMA area.
*could help* - if there is no user, why do we need it? Or do you have a
user?
>
> The CMA supports multiple named CMA areas, and the device could
> use or exclusive a special CAM arae via "cma_area" on "struct
> device". When probing, the device can setup special CMA area which
> find by "cma_find_by_name()".
>
> If device can't find named CMA area, "cma_find_by_name()" will
> return NULL, and device will used default CMA area.
>
> Signed-off-by: BuddyZhang <buddy.zhang@aliyun.com>
> ---
> mm/cma.c | 12 ++++++++++++
> 1 file changed, 12 insertions(+)
>
> diff --git a/mm/cma.c b/mm/cma.c
> index be55d1988c67..b562557572c4 100644
> --- a/mm/cma.c
> +++ b/mm/cma.c
> @@ -40,6 +40,18 @@ struct cma cma_areas[MAX_CMA_AREAS];
> unsigned cma_area_count;
> static DEFINE_MUTEX(cma_mutex);
>
> +struct cma *cma_find_by_name(const char *name)
> +{
> + int idx;
> +
> + for (idx = 0; idx < MAX_CMA_AREAS; idx++) {
> + if (cma_areas[idx].name && !strcmp(name, cma_areas[idx].name))
> + return &cma_areas[idx];
> + }
> + return NULL;
> +}
> +EXPORT_SYMBOL(cma_find_by_name)
> +
> phys_addr_t cma_get_base(const struct cma *cma)
> {
> return PFN_PHYS(cma->base_pfn);
>
--
Thanks,
David / dhildenb
next prev parent reply other threads:[~2020-01-14 9:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-14 7:51 buddy.zhang
2020-01-14 9:02 ` David Hildenbrand [this message]
2020-01-14 10:08 ` buddy.zhang
2020-01-16 4:21 ` kbuild test robot
2020-01-17 4:17 ` kbuild test robot
2020-01-16 10:13 buddy.zhang
2020-01-16 12:12 ` Michal Hocko
2020-01-17 2:16 ` buddy.zhang
2020-01-17 6:28 ` 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=3cb5e071-c5c0-47f8-96e9-526ca5dbfc62@redhat.com \
--to=david@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=buddy.zhang@aliyun.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