All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@sandeen.net>
To: Christoph Hellwig <hch@infradead.org>
Cc: xfs-oss <xfs@oss.sgi.com>
Subject: Re: [PATCH V2] make xfs stats Kconfigurable
Date: Sun, 19 Aug 2007 14:13:52 -0500	[thread overview]
Message-ID: <46C89670.6050101@sandeen.net> (raw)
In-Reply-To: <20070819191010.GC2929@infradead.org>

Christoph Hellwig wrote:
> On Sun, Aug 19, 2007 at 12:21:09PM -0500, Eric Sandeen wrote:
>> Oops, typo in Makefile (CONFIG_XFS_STAT vs _STATS).
>>
>> ----
>>
>>
>> xfs stats are already optional based on CONFIG_PROC_FS, and there
>> is already a (never-set) macro XFS_STATS_OFF which can turn them
>> off.  Making it a configurable option, if I turn them off I can
>> get a little stack savings on x86, gcc 4.1:
> 
> Why would we want to disable the statistics?

To save a little stack space.  :)  *shrug*

This one's not so critical.  FWIW, JFS has configurable stats, and I
think an upcoming jbd patch adds (config-optional) stats.

OTOH when are stats really used outside of sgi?  Though I suppose
occasionally they'd be useful in field debugging.

*shrug* this one may not be worth it; I won't be heartbroken if it
doesn't go in... it helps a tiny bit on the stack side.

-Eric

>> +	config XFS_STATS
> 
> Everywhere else the config statement is not indented, so it probably
> shouldn't be here either.
> 

      reply	other threads:[~2007-08-19 19:13 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-18 20:04 [PATCH] make xfs stats Kconfigurable Eric Sandeen
2007-08-19 17:21 ` [PATCH V2] " Eric Sandeen
2007-08-19 18:34   ` Eric Sandeen
2007-08-19 19:10   ` Christoph Hellwig
2007-08-19 19:13     ` Eric Sandeen [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=46C89670.6050101@sandeen.net \
    --to=sandeen@sandeen.net \
    --cc=hch@infradead.org \
    --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.