From: Jaewon Kim <jaewon31.kim@samsung.com>
To: Michal Nazarewicz <mina86@mina86.com>, Michal Hocko <mhocko@kernel.org>
Cc: gregkh@linuxfoundation.org, akpm@linux-foundation.org,
labbott@redhat.com, m.szyprowski@samsung.com, linux-mm@kvack.org,
linux-kernel@vger.kernel.org, jaewon31.kim@gmail.com
Subject: Re: [PATCH] mm: cma: print allocation failure reason and bitmap status
Date: Mon, 02 Jan 2017 14:42:33 +0900 [thread overview]
Message-ID: <5869E849.1040605@samsung.com> (raw)
In-Reply-To: <xa1tpok6igqb.fsf@mina86.com>
On 2017e?? 01i?? 02i? 1/4 06:59, Michal Nazarewicz wrote:
> On Fri, Dec 30 2016, Michal Hocko wrote:
>> On Fri 30-12-16 16:24:46, Jaewon Kim wrote:
>> [...]
>>> >From 7577cc94da3af27907aa6eec590d2ef51e4b9d80 Mon Sep 17 00:00:00 2001
>>> From: Jaewon Kim <jaewon31.kim@samsung.com>
>>> Date: Thu, 29 Dec 2016 11:00:16 +0900
>>> Subject: [PATCH] mm: cma: print allocation failure reason and bitmap status
>>>
>>> There are many reasons of CMA allocation failure such as EBUSY, ENOMEM, EINTR.
>>> But we did not know error reason so far. This patch prints the error value.
>>>
>>> Additionally if CONFIG_CMA_DEBUG is enabled, this patch shows bitmap status to
>>> know available pages. Actually CMA internally try all available regions because
>>> some regions can be failed because of EBUSY. Bitmap status is useful to know in
>>> detail on both ENONEM and EBUSY;
>>> ENOMEM: not tried at all because of no available region
>>> it could be too small total region or could be fragmentation issue
>>> EBUSY: tried some region but all failed
>>>
>>> This is an ENOMEM example with this patch.
>>> [ 13.250961] [1: Binder:715_1: 846] cma: cma_alloc: alloc failed, req-size: 256 pages, ret: -12
>>> Avabile pages also will be shown if CONFIG_CMA_DEBUG is enabled
>>> [ 13.251052] [1: Binder:715_1: 846] cma: number of available pages: 4@572+7@585+7@601+8@632+38@730+166@1114+127@1921=>357 pages, total: 2048 pages
>> please mention how to interpret this information.
Thank you Michal Hocko. I added like this
If CONFIG_CMA_DEBUG is enabled, avabile pages also will be shown as concatenated
size@position format. So 4@572 means that there are 4 available pages at 572
position starting from 0 position.
>>
>> some more style suggestions below
>>> Signed-off-by: Jaewon Kim <jaewon31.kim@samsung.com>
> Acked-by: Michal Nazarewicz <mina86@mina86.com>
Thank you I added your Ack
Acked-by: Michal Nazarewicz <mina86@mina86.com>
>>> ---
>>> mm/cma.c | 29 ++++++++++++++++++++++++++++-
>>> 1 file changed, 28 insertions(+), 1 deletion(-)
>>>
>>> diff --git a/mm/cma.c b/mm/cma.c
>>> index c960459..1bcd9db 100644
>>> --- a/mm/cma.c
>>> +++ b/mm/cma.c
>>> @@ -369,7 +369,7 @@ struct page *cma_alloc(struct cma *cma, size_t count, unsigned int align)
>>> unsigned long start = 0;
>>> unsigned long bitmap_maxno, bitmap_no, bitmap_count;
>>> struct page *page = NULL;
>>> - int ret;
>>> + int ret = -ENOMEM;
>>>
>>> if (!cma || !cma->count)
>>> return NULL;
>>> @@ -427,6 +427,33 @@ struct page *cma_alloc(struct cma *cma, size_t count, unsigned int align)
>>> trace_cma_alloc(pfn, page, count, align);
>>>
>>> pr_debug("%s(): returned %p\n", __func__, page);
> This line should be moved after the a??if (ret != 0)a?? block, i.e. just
> before return.
Thank you Michal Nazarewicz
I moved the pr_debug right before return
pr_debug("%s(): returned %p\n", __func__, page);
return page;
>>> +
>>> + if (ret != 0)
>> you can simply do
>> if (!ret) {
Thank you
I changed like this, it should be if(ret) rather than if(!ret)
+ if (ret) {
+ pr_info("%s: alloc failed, req-size: %zu pages, ret: %d\n",
+ __func__, count, ret);
+ debug_show_cma_areas(cma);
+ }
>>
>> pr_info("%s: alloc failed, req-size: %zu pages, ret: %d\n",
>> __func__, count, ret);
>> debug_show_cma_areas();
>> }
>>
>> return page;
>>
>> static void debug_show_cma_areas(void)
>> {
>> #ifdef CONFIG_CMA_DEBUG
>> unsigned int nr, nr_total = 0;
>> unsigned long next_set_bit;
>>
>> mutex_lock(&cma->lock);
>> pr_info("number of available pages: ");
>> start = 0;
>> for (;;) {
>> bitmap_no = find_next_zero_bit(cma->bitmap, cma->count, start);
>> if (bitmap_no >= cma->count)
>> break;
>> next_set_bit = find_next_bit(cma->bitmap, cma->count, bitmap_no);
>> nr = next_set_bit - bitmap_no;
>> pr_cont("%s%u@%lu", nr_total ? "+" : "", nr, bitmap_no);
>> nr_total += nr;
>> start = bitmap_no + nr;
>> }
>> pr_cont("=>%u pages, total: %lu pages\n", nr_total, cma->count);
> Perhaps:
> pr_cont("=> %u free of %lu total pages\n", nr_total, cma->count);
Thank you I will take this way.
+ pr_cont("=> %u free of %lu total pages\n", nr_total, cma->count);
> or shorter (but more cryptic):
> pr_cont("=> %u/%lu pages\n", nr_total, cma->count);
>
>> mutex_unlock(&cma->lock);
>> #endif
>> }
> Actually, Linux style is more like:
>
> #ifdef CONFIG_CMA_DEBUG
> static void cma_debug_show_areas()
> {
> a?|
> }
> #else
> static inline void cma_debug_show_areas() { }
> #endif
Thank you I will take this way. FYI struct cma address should be passed as a argument.
+#ifdef CONFIG_CMA_DEBUG
+static void debug_show_cma_areas(struct cma *cma)
+{
...
+#else
+static inline void debug_show_cma_areas(struct cma *cma) { }
+#endif
>> --
>> Michal Hocko
>> SUSE Labs
Thank you all of you.
Let me reattach my full patch to be clear.
Let me know if I resend this as a new mail thread.
next prev parent reply other threads:[~2017-01-02 5:41 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20161229022722epcas5p4be0e1924f3c8d906cbfb461cab8f0374@epcas5p4.samsung.com>
2016-12-29 2:28 ` Jaewon Kim
2016-12-29 9:14 ` Michal Hocko
2016-12-29 9:26 ` Jaewon Kim
2016-12-29 9:43 ` Michal Hocko
2016-12-30 6:27 ` Jaewon Kim
2016-12-29 14:20 ` Michal Nazarewicz
2016-12-30 7:24 ` Jaewon Kim
2016-12-30 9:44 ` Michal Hocko
2017-01-01 21:59 ` Michal Nazarewicz
2017-01-02 5:42 ` Jaewon Kim [this message]
2017-01-02 6:46 ` Michal Nazarewicz
2017-01-02 8:06 ` Jaewon Kim
2017-01-02 8:47 ` 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=5869E849.1040605@samsung.com \
--to=jaewon31.kim@samsung.com \
--cc=akpm@linux-foundation.org \
--cc=gregkh@linuxfoundation.org \
--cc=jaewon31.kim@gmail.com \
--cc=labbott@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=m.szyprowski@samsung.com \
--cc=mhocko@kernel.org \
--cc=mina86@mina86.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