public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Eric Sandeen <sandeen@sandeen.net>
To: Dave Chinner <david@fromorbit.com>
Cc: Akshay Lal <akshaylal@google.com>, xfs@oss.sgi.com
Subject: Re: [PATCH] xfstests: made test 215 backwards compatible with	older version of bash.
Date: Wed, 31 Mar 2010 18:47:00 -0500	[thread overview]
Message-ID: <4BB3DEF4.5030208@sandeen.net> (raw)
In-Reply-To: <20100331223321.GJ7671@dastard>

Dave Chinner wrote:
> On Wed, Mar 31, 2010 at 12:06:33PM -0700, Akshay Lal wrote:
>> Test 215 fails on older versions of bash (2.x), mainly due to the use of
>> 'let' for arithemetic operations. Changed to 'expr'.
> 
> If that is a problem for older bash versions, then there's going
> systemic problems throughout the xfstests suite. The let expression
> is used about 80 different places, and I don't see anything special
> about test 215 that makes it any different from other uses. i might
> be missing something, but there's not much context to go on from
> your changelog....
> 
> Perhaps upgrading your version of bash might be a better approach?
> 
> Cheers,
> 
> Dave.

Also, a wholesale switch from expr to let was done not long ago, for
very specific reasons - see below - so I don't think there's much 
interest in going back in the other direction.

Thanks,
-Eric

commit e714acc0ef37031b9a5a522703f2832f139c22e0
Author: Dave Chinner <david@fromorbit.com>
Date:   Wed Mar 25 20:53:36 2009 +0100

    reduce the number of processes forked
    
    One of the big cpu time consumers when running xfsqa on UML
    is forking of new processes. when looping lots of times,
    using 'expr' to calculate the loop counter increment means
    we fork at least once every loop. using shell builtins means
    that we don't fork and many tests run substantially faster.
    
    Some tests are even runnable with this modification. e.g. 110
    went from taking 4500s to run down to 9s with the loop iterators
    changed to avoid forking.
    
    Signed-off-by: Dave Chinner <david@fromorbit.com>
    Signed-off-by: Christoph Hellwig <hch@lst.de>

diff --git a/007 b/007
index e8c6610..290f716 100755
--- a/007
+++ b/007
@@ -50,7 +50,7 @@ num_filenames=100
 i=1
 while [ $i -le $num_filenames ]; do
   echo "nametest.$i" >>$sourcefile
-  i=`expr $i + 1`
+  let i=$i+1
 done
 
 mkdir $testdir/$seq

.... etc ....

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

      reply	other threads:[~2010-03-31 23:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Fix for test 215>
2010-03-31 19:06 ` [PATCH] xfstests: made test 215 backwards compatible with older version of bash Akshay Lal
2010-03-31 22:33   ` Dave Chinner
2010-03-31 23:47     ` 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=4BB3DEF4.5030208@sandeen.net \
    --to=sandeen@sandeen.net \
    --cc=akshaylal@google.com \
    --cc=david@fromorbit.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