public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Chinner <david@fromorbit.com>
To: xfs@oss.sgi.com
Subject: [PATCH 0/3] [XFSQA] Optimisations and ENOSPC tests
Date: Sun, 15 Mar 2009 21:49:38 +1100	[thread overview]
Message-ID: <1237114181-18431-1-git-send-email-david@fromorbit.com> (raw)

The first patch reduces the number of forks required by some
qa tests by using shell builtins. Tests run faster on UML
if they fork less.

The other two patches introduce tests that trip over
spurious ENOSPC errors. A followup patch series will fix
these test failures.

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

             reply	other threads:[~2009-03-15 14:08 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-15 10:49 Dave Chinner [this message]
2009-03-15 10:49 ` [PATCH 1/3] [XFSQA] Reduce the number of processes forked Dave Chinner
2009-03-16  6:23   ` Christoph Hellwig
2009-03-15 10:49 ` [PATCH 2/3] [XFSQA] Add simple delayed allocation ENOSPC test Dave Chinner
2009-03-16  6:23   ` Christoph Hellwig
2009-03-15 10:49 ` [PATCH 3/3] [XFSQA] Test writing to ENOSPC Dave Chinner
2009-03-16  6:27   ` 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=1237114181-18431-1-git-send-email-david@fromorbit.com \
    --to=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