From: Dave Chinner <david@fromorbit.com>
To: Chandra Seetharaman <sekharan@us.ibm.com>
Cc: Brian Foster <bfoster@redhat.com>, xfs@oss.sgi.com
Subject: Re: [PATCH V2] xfs: introduce CONFIG_XFS_WARN
Date: Fri, 26 Apr 2013 07:44:05 +1000 [thread overview]
Message-ID: <20130425214405.GR30622@dastard> (raw)
In-Reply-To: <1366898869.3762.32410.camel@chandra-dt.ibm.com>
On Thu, Apr 25, 2013 at 09:07:49AM -0500, Chandra Seetharaman wrote:
> On Thu, 2013-04-25 at 08:58 +1000, 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.
>
> Thanks for the clarification.
>
> I was thinking that CONFIG_XFS_DEBUG would be enabled in the distro's
> debug kernel and this new option is in addition to that. Hence, my
> question.
If you are shipping a debug kernel with CONFIG_XFS_DEBUG, then you
don't want your customers running that debug kernel for very long.
CONFIG_XFS_DEBUG changes allocation algorithms to improve test
coverage and this causes accelerated filesystem aging....
CONFIG_XFS_WARN is designed to be used instead of CONFIG_XFS_DEBUG
in these situations - we get more verbose checking, but without the
down sides associated with all the algorithmic changes in
XFS_DEBUG...
> So, with this new config option, CONFIG_XFS_DEBUG will only be used in
> development environment, correct ?
That's what I has always been intended for.
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2013-04-25 21:44 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
2013-04-25 14:07 ` Chandra Seetharaman
2013-04-25 21:44 ` Dave Chinner [this message]
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=20130425214405.GR30622@dastard \
--to=david@fromorbit.com \
--cc=bfoster@redhat.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.