From: Eric Sandeen <sandeen@sandeen.net>
To: Dave Chinner <david@fromorbit.com>
Cc: Brian Foster <bfoster@redhat.com>,
Chandra Seetharaman <sekharan@us.ibm.com>,
xfs@oss.sgi.com
Subject: Re: [PATCH V2] xfs: introduce CONFIG_XFS_WARN
Date: Wed, 24 Apr 2013 19:21:17 -0500 [thread overview]
Message-ID: <517876FD.1000508@sandeen.net> (raw)
In-Reply-To: <20130424225821.GV10481@dastard>
On 4/24/13 5:58 PM, Dave Chinner wrote:
> On Wed, Apr 24, 2013 at 01:39:52PM -0500, Chandra Seetharaman wrote:
>> Hi Dave,
>>
>> Since this solution is for production environment, would it be valuable
>> to have a sysctl variable to allow enabling/disabling XFS_WARN, as
>> opposed to needing to recompile the module afresh ?
>
> The idea is that distros enable it on the debug kernel packages
> rather than using CONFIG_XFS_DEBUG=y. Hence if someone has a
> problem, they just install the debug kernel and they get all this
> additional checking.
>
> There are roughly 1700 ASSERT statements in the XFS code, so
> compiling them in unconditionally is a lot of extra code. Adding a
> sysctl to make them conditional adds as many branches into the code
> than in 99.99999% of calls are never going to evaluate as true. The
> convenience of a sysctl is more than outweighed by the additional
> overhead for the majortiy of people that don't need to diagnose
> problems on their system.
>
> Hence I don't think the overhead of unconditionally compiling in
> ASSERT checks is worth while for the majority of users, especially
> as most distros ship a debug kernel for exactly this purpose....
I agree. kernel-debug, or whatever your distro does similarly,
is the right use for this code.
-Eric
> Cheers,
>
> Dave.
>
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2013-04-25 0:21 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-23 6:38 [PATCH] xfs: introduce CONFIG_XFS_WARN Dave Chinner
2013-04-23 12:49 ` Brian Foster
2013-04-23 21:02 ` Dave Chinner
2013-04-24 8:55 ` [PATCH V2] " Dave Chinner
2013-04-24 18:39 ` Chandra Seetharaman
2013-04-24 22:58 ` Dave Chinner
2013-04-25 0:21 ` Eric Sandeen [this message]
2013-04-25 14:07 ` Chandra Seetharaman
2013-04-25 21:44 ` Dave Chinner
2013-04-25 22:29 ` Chandra Seetharaman
2013-04-25 14:48 ` Brian Foster
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=517876FD.1000508@sandeen.net \
--to=sandeen@sandeen.net \
--cc=bfoster@redhat.com \
--cc=david@fromorbit.com \
--cc=sekharan@us.ibm.com \
--cc=xfs@oss.sgi.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 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.