From: Christoph Hellwig <hch@infradead.org>
To: Eric Sandeen <sandeen@sandeen.net>
Cc: Christoph Hellwig <hch@infradead.org>,
linux-ia64@vger.kernel.org, Steven Rostedt <rostedt@goodmis.org>,
xfs@oss.sgi.com
Subject: Re: [PATCH, RFC] xfs: event tracing support
Date: Fri, 17 Jul 2009 10:09:55 -0400 [thread overview]
Message-ID: <20090717140955.GA26050@infradead.org> (raw)
In-Reply-To: <4A5FA82F.6050903@sandeen.net>
On Thu, Jul 16, 2009 at 05:22:39PM -0500, Eric Sandeen wrote:
> Where are we at with this one, I'd like to get this in for XFS but I
> agree w/ Felix that throwing out a "working" trace infrastructure w/
> nothing to replace it on ia64 would not be great.
Well, it's not actuall working in these sense of that it isn't and never
has been in mainline and also is utterly bit-rotted. I have absolutely
no interested in keeping a tracing implementation away from mainline
that just works out of the box (not just on x86 but also on powerpc and
others) just because ia64 is too slow to get modern features.
And it's not like we got any interesting amount of IA64 users, nor have
does SGI who seems to be interested in IA64 do a lot of patches to XFS.
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2009-07-17 14:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-16 21:48 [PATCH, RFC] xfs: event tracing support Christoph Hellwig
2009-06-22 18:01 ` Felix Blyakher
2009-06-22 20:59 ` Christoph Hellwig
2009-06-22 21:37 ` Felix Blyakher
2009-07-16 22:22 ` Eric Sandeen
2009-07-16 22:35 ` Steven Rostedt
2009-07-17 14:09 ` Christoph Hellwig [this message]
2009-07-17 14:50 ` [PATCH] " Christoph Hellwig
2009-07-17 18:04 ` Christoph Hellwig
2009-07-17 18:40 ` Eric Sandeen
2009-07-18 14:02 ` 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=20090717140955.GA26050@infradead.org \
--to=hch@infradead.org \
--cc=linux-ia64@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=sandeen@sandeen.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox