linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: John Hubbard <jhubbard@nvidia.com>
To: Minchan Kim <minchan@kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>
Cc: linux-mm <linux-mm@kvack.org>,
	LKML <linux-kernel@vger.kernel.org>, <surenb@google.com>,
	<joaodias@google.com>
Subject: Re: [PATCH] mm: vmstat: add cma statistics
Date: Wed, 17 Feb 2021 12:57:25 -0800	[thread overview]
Message-ID: <8036d8e6-8e96-7b4e-91c0-e1ae91b637e1@nvidia.com> (raw)
In-Reply-To: <20210217170025.512704-1-minchan@kernel.org>

On 2/17/21 9:00 AM, Minchan Kim wrote:
> Since CMA is used more widely, it's worth to have CMA
> allocation statistics into vmstat. With it, we could
> know how agressively system uses cma allocation and
> how often it fails.
> 
> Signed-off-by: Minchan Kim <minchan@kernel.org>
> ---
>   include/linux/vm_event_item.h |  3 +++
>   mm/cma.c                      | 12 +++++++++---
>   mm/vmstat.c                   |  4 ++++
>   3 files changed, 16 insertions(+), 3 deletions(-)
> 
> diff --git a/include/linux/vm_event_item.h b/include/linux/vm_event_item.h
> index 18e75974d4e3..0c567014ce82 100644
> --- a/include/linux/vm_event_item.h
> +++ b/include/linux/vm_event_item.h
> @@ -70,6 +70,9 @@ enum vm_event_item { PGPGIN, PGPGOUT, PSWPIN, PSWPOUT,
>   #endif
>   #ifdef CONFIG_HUGETLB_PAGE
>   		HTLB_BUDDY_PGALLOC, HTLB_BUDDY_PGALLOC_FAIL,
> +#endif
> +#ifdef CONFIG_CMA
> +		CMA_ALLOC, CMA_ALLOC_FAIL,

This seems wrong: here it's called "alloc", but in the output it's
called "alloc success", and in the implementation it's clearly
"alloc attempt" that is being counted.

Once these are all made consistent, then the bug should naturally
go away as part of that.

nit: I think the multiple items per line is a weak idea at best, even
though it's used here already. Each item is important and needs to be
visually compared to it's output item later. So one per line might
have helped avoid mismatches, and I think we should change to that to
encourage that trend.

thanks,
-- 
John Hubbard
NVIDIA

>   #endif
>   		UNEVICTABLE_PGCULLED,	/* culled to noreclaim list */
>   		UNEVICTABLE_PGSCANNED,	/* scanned for reclaimability */
> diff --git a/mm/cma.c b/mm/cma.c
> index 23d4a97c834a..ea1e39559526 100644
> --- a/mm/cma.c
> +++ b/mm/cma.c
> @@ -434,14 +434,16 @@ struct page *cma_alloc(struct cma *cma, size_t count, unsigned int align,
>   	struct page *page = NULL;
>   	int ret = -ENOMEM;
>   
> +	count_vm_event(CMA_ALLOC);
> +
>   	if (!cma || !cma->count || !cma->bitmap)
> -		return NULL;
> +		goto out;
>   
>   	pr_debug("%s(cma %p, count %zu, align %d)\n", __func__, (void *)cma,
>   		 count, align);
>   
>   	if (!count)
> -		return NULL;
> +		goto out;
>   
>   	mask = cma_bitmap_aligned_mask(cma, align);
>   	offset = cma_bitmap_aligned_offset(cma, align);
> @@ -449,7 +451,7 @@ struct page *cma_alloc(struct cma *cma, size_t count, unsigned int align,
>   	bitmap_count = cma_bitmap_pages_to_bits(cma, count);
>   
>   	if (bitmap_count > bitmap_maxno)
> -		return NULL;
> +		goto out;
>   
>   	for (;;) {
>   		mutex_lock(&cma->lock);
> @@ -506,6 +508,10 @@ struct page *cma_alloc(struct cma *cma, size_t count, unsigned int align,
>   	}
>   
>   	pr_debug("%s(): returned %p\n", __func__, page);
> +out:
> +	if (!page)
> +		count_vm_event(CMA_ALLOC_FAIL);
> +
>   	return page;
>   }
>   
> diff --git a/mm/vmstat.c b/mm/vmstat.c
> index 97fc32a53320..d8c32a33208d 100644
> --- a/mm/vmstat.c
> +++ b/mm/vmstat.c
> @@ -1305,6 +1305,10 @@ const char * const vmstat_text[] = {
>   #ifdef CONFIG_HUGETLB_PAGE
>   	"htlb_buddy_alloc_success",
>   	"htlb_buddy_alloc_fail",
> +#endif
> +#ifdef CONFIG_CMA
> +	"cma_alloc_success",
> +	"cma_alloc_fail",
>   #endif
>   	"unevictable_pgs_culled",
>   	"unevictable_pgs_scanned",
> 



  reply	other threads:[~2021-02-17 20:57 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-17 17:00 Minchan Kim
2021-02-17 20:57 ` John Hubbard [this message]
2021-02-17 21:19   ` Minchan Kim

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=8036d8e6-8e96-7b4e-91c0-e1ae91b637e1@nvidia.com \
    --to=jhubbard@nvidia.com \
    --cc=akpm@linux-foundation.org \
    --cc=joaodias@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=minchan@kernel.org \
    --cc=surenb@google.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