linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Nikolay Borisov <nborisov@suse.com>
To: Lukasz Luba <l.luba@partner.samsung.com>, linux-kernel@vger.kernel.org
Cc: b.zolnierkie@samsung.com, longman@redhat.com, mingo@redhat.com
Subject: Re: [PATCH] lib/Kconfig.debug: add a comment to PROVE_LOCKING impact
Date: Tue, 9 Oct 2018 18:53:54 +0300	[thread overview]
Message-ID: <720c53a6-30c4-19f9-d971-8c1d6054c149@suse.com> (raw)
In-Reply-To: <20181009153959eucas1p1ab3c10ba4868a4e97a1bff24d8f34c41~b_u5xrZ3z3130331303eucas1p1U@eucas1p1.samsung.com>



On  9.10.2018 18:39, Lukasz Luba wrote:
> This patch add some comment related to performance impact,
> which can be really big (x3 times slower context switch).
> 
> Signed-off-by: Lukasz Luba <l.luba@partner.samsung.com>

I don't think this brings any value. lockdep is a debugging aid aimed at
developers. A developer should be aware that it has a performance impact
and the classification x3 doesn't really bring anything.
> ---
>  lib/Kconfig.debug | 11 +++++++++++
>  1 file changed, 11 insertions(+)
> 
> diff --git a/lib/Kconfig.debug b/lib/Kconfig.debug
> index 4966c4f..9e67a2a3 100644
> --- a/lib/Kconfig.debug
> +++ b/lib/Kconfig.debug
> @@ -1088,6 +1088,9 @@ config PROVE_LOCKING
>  	 the proof of observed correctness is also maintained for an
>  	 arbitrary combination of these separate locking variants.
>  
> +	 This feature enables LOCKDEP which can harm system performance
> +	 even x3 times.
> +
>  	 For more details, see Documentation/locking/lockdep-design.txt.
>  
>  config LOCK_STAT
> @@ -1112,6 +1115,10 @@ config LOCK_STAT
>  	 CONFIG_LOCK_STAT defines "contended" and "acquired" lock events.
>  	 (CONFIG_LOCKDEP defines "acquire" and "release" events.)
>  
> +	 This feature enables LOCKDEP which can harm system performance
> +	 even x3 times.
> +	 For more details, see Documentation/locking/lockdep-design.txt.
> +
>  config DEBUG_RT_MUTEXES
>  	bool "RT Mutex debugging, deadlock detection"
>  	depends on DEBUG_KERNEL && RT_MUTEXES
> @@ -1175,6 +1182,10 @@ config DEBUG_LOCK_ALLOC
>  	 spin_lock_init()/mutex_init()/etc., or whether there is any lock
>  	 held during task exit.
>  
> +	 This feature enables LOCKDEP which can harm system performance
> +	 even x3 times.
> +	 For more details, see Documentation/locking/lockdep-design.txt.
> +
>  config LOCKDEP
>  	bool
>  	depends on DEBUG_KERNEL && LOCK_DEBUGGING_SUPPORT
> 

  reply	other threads:[~2018-10-09 15:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20181009153959eucas1p1ab3c10ba4868a4e97a1bff24d8f34c41@eucas1p1.samsung.com>
2018-10-09 15:39 ` [PATCH] lib/Kconfig.debug: add a comment to PROVE_LOCKING impact Lukasz Luba
2018-10-09 15:53   ` Nikolay Borisov [this message]
2018-10-09 17:29   ` Waiman Long
2018-10-10  8:42     ` Lukasz Luba

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=720c53a6-30c4-19f9-d971-8c1d6054c149@suse.com \
    --to=nborisov@suse.com \
    --cc=b.zolnierkie@samsung.com \
    --cc=l.luba@partner.samsung.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=longman@redhat.com \
    --cc=mingo@redhat.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).