From: Dave Chinner <david@fromorbit.com>
To: Philip White <pwhite@sgi.com>
Cc: xfs@oss.sgi.com
Subject: Re: [PATCH 02/18] xfstests: Clear out old benchmarking materials
Date: Fri, 15 Mar 2013 15:05:31 +1100 [thread overview]
Message-ID: <20130315040531.GH21651@dastard> (raw)
In-Reply-To: <20130314130611.4A3C153DEAF1@polaris-admin.engr.sgi.com>
On Thu, Mar 14, 2013 at 06:06:11AM -0700, Philip White wrote:
> From: Phil White <pwhite@sgi.com>
>
>
> This is a rebasing & resubmit of a dchinner patch. His comments on the
> original:
> -----------------
> The benchmark framework inside xfstests is basically unused,
> bitrotted and not very useful. If we need benchmarks, lets use a
> real benchmark framework, not xfstests. Kill it to remove
> dependencies on common and common.rc.
> -----------------
>
> The current benchmark framework has bitrotted, but it is not without value
> in my view. It should be removed and updated. In the interest of future
> useability, I have kept the dependencies on common and common.rc.
This makes no sense - you've removed everything but the bench
script, which can't do anything without all the bits you just
removed. But you still want to keep a useless script and it's
dependencies around "just because".
Let go of bench. Re-implement it from scratch rather than try to
shoehorn it into the stub of the old, bitrotted code. IOWs, any new
benchmarking infrastructure needs to abstravct and document each
dependency it adds to the common code - that way we don't end up
with keeping unnecessary dependencies around or trying to shoehorn
new code into abstractions that don't make sense.
FWIW, this comes back to what I said about having a patch series
description - I didn't realise at first that you hadn't completely
removed all of the bench infrastructure because there was no
overview of what you'd done. Hence it's only now that I'm looking
at the patches in detail have I noticed this subtle change you made
to my original patch set....
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2013-03-15 4:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-14 13:06 [PATCH 02/18] xfstests: Clear out old benchmarking materials Philip White
2013-03-15 4:05 ` Dave Chinner [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=20130315040531.GH21651@dastard \
--to=david@fromorbit.com \
--cc=pwhite@sgi.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox