From: Michal Hocko <mhocko@kernel.org>
To: Jaewon Kim <jaewon31.kim@samsung.com>
Cc: gregkh@linuxfoundation.org, akpm@linux-foundation.org,
labbott@redhat.com, mina86@mina86.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: Thu, 29 Dec 2016 10:43:36 +0100 [thread overview]
Message-ID: <20161229094335.GH29208@dhcp22.suse.cz> (raw)
In-Reply-To: <5864D6CE.7070001@samsung.com>
On Thu 29-12-16 18:26:38, Jaewon Kim wrote:
>
>
> On 2016e?? 12i?? 29i? 1/4 18:14, Michal Hocko wrote:
> > On Thu 29-12-16 11:28:02, Jaewon Kim wrote:
> >> There are many reasons of CMA allocation failure such as EBUSY, ENOMEM, EINTR.
> >> This patch prints the error value and bitmap status to know available pages
> >> regarding fragmentation.
> >>
> >> This is an ENOMEM example with this patch.
> >> [ 11.616321] [2: Binder:711_1: 740] cma: cma_alloc: alloc failed, req-size: 256 pages, ret: -12
> >> [ 11.616365] [2: Binder:711_1: 740] number of available pages: 4+7+7+8+38+166+127=>357 pages, total: 2048 pages
> > Could you be more specific why this part is useful?
> Hi
> Without this patch we do not know why CMA allocation failed.
Yes, I understand the first part
> Additionally in case of ENOMEM, with bitmap status we can figure out that
The code doesn't seem to check for ENOMEM though
> if it is too small CMA region issue or if it is fragmentation issue.
then please describe that in the changelog. If I got it right the above
would tell us that the fragmentation is the problem, right?
> >
> >> Signed-off-by: Jaewon Kim <jaewon31.kim@samsung.com>
> >> ---
> >> mm/cma.c | 29 ++++++++++++++++++++++++++++-
> >> 1 file changed, 28 insertions(+), 1 deletion(-)
> >>
> >> diff --git a/mm/cma.c b/mm/cma.c
> >> index c960459..535aa39 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);
> >> +
> >> + if (ret != 0) {
> >> + unsigned int nr, nr_total = 0;
> >> + unsigned long next_set_bit;
> >> +
> >> + pr_info("%s: alloc failed, req-size: %zu pages, ret: %d\n",
> >> + __func__, count, ret);
> >> + mutex_lock(&cma->lock);
> >> + printk("number of available pages: ");
I guess you want pr_info (or maybe pr_debug) here
> >> + start = 0;
> >> + for (;;) {
> >> + bitmap_no = find_next_zero_bit(cma->bitmap, cma->count, start);
> >> + next_set_bit = find_next_bit(cma->bitmap, cma->count, bitmap_no);
> >> + nr = next_set_bit - bitmap_no;
> >> + if (bitmap_no >= cma->count)
> >> + break;
> >> + if (nr_total == 0)
> >> + printk("%u", nr);
> >> + else
> >> + printk("+%u", nr);
pr_cont
> >> + nr_total += nr;
> >> + start = bitmap_no + nr;
> >> + }
> >> + printk("=>%u pages, total: %lu pages\n", nr_total, cma->count);
pr_cont
> >> + mutex_unlock(&cma->lock);
> >> + }
> >> +
> >> return page;
> >> }
> >>
> >> --
> >> 1.9.1
> >>
> >> --
> >> To unsubscribe, send a message with 'unsubscribe linux-mm' in
> >> the body to majordomo@kvack.org. For more info on Linux MM,
> >> see: http://www.linux-mm.org/ .
> >> Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
>
> --
> To unsubscribe, send a message with 'unsubscribe linux-mm' in
> the body to majordomo@kvack.org. For more info on Linux MM,
> see: http://www.linux-mm.org/ .
> Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
--
Michal Hocko
SUSE Labs
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2016-12-29 9:43 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 ` [PATCH] mm: cma: print allocation failure reason and bitmap status Jaewon Kim
2016-12-29 9:14 ` Michal Hocko
2016-12-29 9:26 ` Jaewon Kim
2016-12-29 9:43 ` Michal Hocko [this message]
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
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=20161229094335.GH29208@dhcp22.suse.cz \
--to=mhocko@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=gregkh@linuxfoundation.org \
--cc=jaewon31.kim@gmail.com \
--cc=jaewon31.kim@samsung.com \
--cc=labbott@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=m.szyprowski@samsung.com \
--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;
as well as URLs for NNTP newsgroup(s).