From: Joe Perches <joe@perches.com>
To: Dave Chinner <david@fromorbit.com>,
"Theodore Y. Ts'o" <tytso@mit.edu>,
Eric Sandeen <sandeen@sandeen.net>,
"Darrick J. Wong" <darrick.wong@oracle.com>,
Christoph Hellwig <hch@lst.de>,
linux-xfs@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] xfs: Remove noinline from #define STATIC
Date: Mon, 12 Nov 2018 20:23:42 -0800 [thread overview]
Message-ID: <b03fda08ee4ca4b488c6f67e64bfc94f49be4e83.camel@perches.com> (raw)
In-Reply-To: <20181113030926.GQ19305@dastard>
On Tue, 2018-11-13 at 14:09 +1100, Dave Chinner wrote:
> On Mon, Nov 12, 2018 at 08:54:10PM -0500, Theodore Y. Ts'o wrote:
> > On Tue, Nov 13, 2018 at 12:18:05PM +1100, Dave Chinner wrote:
> > > I'm not interested in making code fast if distro support engineers
> > > can't debug problems on user systems easily. Optimising for
> > > performance over debuggability is a horrible trade off for us to
> > > make because it means users and distros end up much more reliant on
> > > single points of expertise for debugging problems. And that means
> > > the majority of the load of problem triage falls directly on very
> > > limited resources - the core XFS development team. A little bit of
> > > thought about how to make code easier to triage and debug goes a
> > > long, long way....
> >
> > So at least in my experience, if the kernels are compiled with
> > CONFIG_DEBUG_INFO and/or CONFIG_DEBUG_INFO_REDUCED,
> > scripts/decode_stracktrace.sh seems to do a very nice job with inlined
>
> That doesn't help with kernel profiling and other such things that
> are based on callgraphs...
If that's really the case:
I rather suspect the xfs static v STATIC function marking is not
particularly curated and the marking is somewhat arbitrary.
So perhaps given the large number of static, but not STATIC
functions, perhaps a sed of s/static/STATIC/ should be done
when it's not inline for all xfs functions.
next prev parent reply other threads:[~2018-11-13 4:23 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-11 1:21 Joe Perches
2018-11-12 20:12 ` Eric Sandeen
2018-11-12 21:05 ` Joe Perches
2018-11-12 21:45 ` Dave Chinner
2018-11-12 22:30 ` Joe Perches
2018-11-13 1:18 ` Dave Chinner
2018-11-13 1:54 ` Theodore Y. Ts'o
2018-11-13 3:09 ` Dave Chinner
2018-11-13 4:23 ` Joe Perches [this message]
2018-11-13 5:26 ` Dave Chinner
2018-11-13 5:31 ` Joe Perches
2018-11-13 5:44 ` Darrick J. Wong
2018-11-15 10:12 ` Christoph Hellwig
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=b03fda08ee4ca4b488c6f67e64bfc94f49be4e83.camel@perches.com \
--to=joe@perches.com \
--cc=darrick.wong@oracle.com \
--cc=david@fromorbit.com \
--cc=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=sandeen@sandeen.net \
--cc=tytso@mit.edu \
/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
all inboxes | Powered by JetHome®