All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michal Nazarewicz <mina86@mina86.com>
To: Michal Hocko <mhocko@kernel.org>, Jaewon Kim <jaewon31.kim@samsung.com>
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: Thu, 29 Dec 2016 15:20:07 +0100	[thread overview]
Message-ID: <xa1th95m7r6w.fsf@mina86.com> (raw)
In-Reply-To: <20161229091449.GG29208@dhcp22.suse.cz>

On Thu, Dec 29 2016, 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?
>  
>> 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: ");
>> +		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;

Put this just next to ‘bitmap_no = …’ line.  No need to call
find_next_bit if we’re gonna break anyway.

>> +			if (nr_total == 0)
>> +				printk("%u", nr);
>> +			else
>> +				printk("+%u", nr);

Perhaps also include location of the hole?  Something like:

		pr_cont("%s%u@%u", nr_total ? "+" : "", nr, bitmap_no);

>> +			nr_total += nr;
>> +			start = bitmap_no + nr;
>> +		}
>> +		printk("=>%u pages, total: %lu pages\n", nr_total, cma->count);
>> +		mutex_unlock(&cma->lock);
>> +	}
>> +

I wonder if this should be wrapped in

#ifdef CMA_DEBUG
…
#endif

On one hand it’s relatively expensive (even involving mutex locking) on
the other it’s in allocation failure path.

>>  	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>
>
> -- 
> Michal Hocko
> SUSE Labs

-- 
Best regards
ミハウ “𝓶𝓲𝓷𝓪86” ナザレヴイツ
«If at first you don’t succeed, give up skydiving»

--
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>

WARNING: multiple messages have this Message-ID (diff)
From: Michal Nazarewicz <mina86@mina86.com>
To: Michal Hocko <mhocko@kernel.org>, Jaewon Kim <jaewon31.kim@samsung.com>
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: Thu, 29 Dec 2016 15:20:07 +0100	[thread overview]
Message-ID: <xa1th95m7r6w.fsf@mina86.com> (raw)
In-Reply-To: <20161229091449.GG29208@dhcp22.suse.cz>

On Thu, Dec 29 2016, 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?
>  
>> 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: ");
>> +		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;

Put this just next to ‘bitmap_no = …’ line.  No need to call
find_next_bit if we’re gonna break anyway.

>> +			if (nr_total == 0)
>> +				printk("%u", nr);
>> +			else
>> +				printk("+%u", nr);

Perhaps also include location of the hole?  Something like:

		pr_cont("%s%u@%u", nr_total ? "+" : "", nr, bitmap_no);

>> +			nr_total += nr;
>> +			start = bitmap_no + nr;
>> +		}
>> +		printk("=>%u pages, total: %lu pages\n", nr_total, cma->count);
>> +		mutex_unlock(&cma->lock);
>> +	}
>> +

I wonder if this should be wrapped in

#ifdef CMA_DEBUG
…
#endif

On one hand it’s relatively expensive (even involving mutex locking) on
the other it’s in allocation failure path.

>>  	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>
>
> -- 
> Michal Hocko
> SUSE Labs

-- 
Best regards
ミハウ “𝓶𝓲𝓷𝓪86” ナザレヴイツ
«If at first you don’t succeed, give up skydiving»

  parent reply	other threads:[~2016-12-29 14:20 UTC|newest]

Thread overview: 26+ 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  2:28   ` Jaewon Kim
2016-12-29  9:14   ` Michal Hocko
2016-12-29  9:14     ` Michal Hocko
2016-12-29  9:26     ` Jaewon Kim
2016-12-29  9:26       ` Jaewon Kim
2016-12-29  9:43       ` Michal Hocko
2016-12-29  9:43         ` Michal Hocko
2016-12-30  6:27         ` Jaewon Kim
2016-12-30  6:27           ` Jaewon Kim
2016-12-29 14:20     ` Michal Nazarewicz [this message]
2016-12-29 14:20       ` Michal Nazarewicz
2016-12-30  7:24       ` Jaewon Kim
2016-12-30  7:24         ` Jaewon Kim
2016-12-30  9:44         ` Michal Hocko
2016-12-30  9:44           ` Michal Hocko
2017-01-01 21:59           ` Michal Nazarewicz
2017-01-01 21:59             ` Michal Nazarewicz
2017-01-02  5:42             ` Jaewon Kim
2017-01-02  5:42               ` Jaewon Kim
2017-01-02  6:46               ` Michal Nazarewicz
2017-01-02  6:46                 ` Michal Nazarewicz
2017-01-02  8:06                 ` Jaewon Kim
2017-01-02  8:06                   ` Jaewon Kim
2017-01-02  8:47             ` Michal Hocko
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=xa1th95m7r6w.fsf@mina86.com \
    --to=mina86@mina86.com \
    --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=mhocko@kernel.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 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.