linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: David Hildenbrand <david@redhat.com>
To: Suren Baghdasaryan <surenb@google.com>, akpm@linux-foundation.org
Cc: torvalds@linux-foundation.org, lstoakes@gmail.com,
	vbabka@suse.cz, linux-mm@kvack.org, linux-kernel@vger.kernel.org,
	kernel-team@android.com
Subject: Re: [PATCH 1/1] mm: change per-VMA lock statistics to be disabled by default
Date: Tue, 2 May 2023 13:27:41 +0200	[thread overview]
Message-ID: <5574983a-3b32-f519-9012-a66b319fc6a8@redhat.com> (raw)
In-Reply-To: <20230428173533.18158-1-surenb@google.com>

On 28.04.23 19:35, Suren Baghdasaryan wrote:
> Change CONFIG_PER_VMA_LOCK_STATS to be disabled by default, as most
> users don't need it. Add configuration help to clarify its usage.
> 
> Fixes: 52f238653e45 ("mm: introduce per-VMA lock statistics")
> Suggested-by: Linus Torvalds <torvalds@linux-foundation.org>
> Signed-off-by: Suren Baghdasaryan <surenb@google.com>
> ---
>   mm/Kconfig.debug | 10 ++++++++--
>   1 file changed, 8 insertions(+), 2 deletions(-)
> 
> diff --git a/mm/Kconfig.debug b/mm/Kconfig.debug
> index 6dae63b46368..a925415b4d10 100644
> --- a/mm/Kconfig.debug
> +++ b/mm/Kconfig.debug
> @@ -274,6 +274,12 @@ config DEBUG_KMEMLEAK_AUTO_SCAN
>   config PER_VMA_LOCK_STATS
>   	bool "Statistics for per-vma locks"
>   	depends on PER_VMA_LOCK
> -	default y
>   	help
> -	  Statistics for per-vma locks.
> +	  Say Y here to enable success, retry and failure counters of page
> +	  faults handled under protection of per-vma locks. When enabled, the
> +	  counters are exposed in /proc/vmstat. This information is useful for
> +	  kernel developers to evaluate effectiveness of per-vma locks and to
> +	  identify pathological cases. Counting these events introduces a small
> +	  overhead in the page fault path.
> +
> +	  If in doubt, say N.

Reviewed-by: David Hildenbrand <david@redhat.com>

-- 
Thanks,

David / dhildenb


      parent reply	other threads:[~2023-05-02 15:59 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-28 17:35 Suren Baghdasaryan
2023-04-28 17:40 ` Lorenzo Stoakes
2023-05-02 10:00 ` Vlastimil Babka
2023-05-02 11:27 ` David Hildenbrand [this message]

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=5574983a-3b32-f519-9012-a66b319fc6a8@redhat.com \
    --to=david@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=kernel-team@android.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=lstoakes@gmail.com \
    --cc=surenb@google.com \
    --cc=torvalds@linux-foundation.org \
    --cc=vbabka@suse.cz \
    /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