public inbox for fstests@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Chinner <david@fromorbit.com>
To: "Lukáš Czerner" <lczerner@redhat.com>
Cc: Eryu Guan <eguan@redhat.com>, fstests@vger.kernel.org
Subject: Re: [PATCH] generic: concurrent IO test with mixed IO types
Date: Wed, 10 Jun 2015 08:27:09 +1000	[thread overview]
Message-ID: <20150609222709.GB24666@dastard> (raw)
In-Reply-To: <alpine.LFD.2.00.1506081300400.1273@localhost.localdomain>

On Mon, Jun 08, 2015 at 01:02:48PM +0200, Lukáš Czerner wrote:
> On Mon, 8 Jun 2015, Eryu Guan wrote:
> 
> > Date: Mon,  8 Jun 2015 18:41:41 +0800 From: Eryu Guan
> > <eguan@redhat.com> To: fstests@vger.kernel.org Cc:
> > lczerner@redhat.com, Eryu Guan <eguan@redhat.com> Subject:
> > [PATCH] generic: concurrent IO test with mixed IO types
> > 
> > Test concurrent buffered I/O, DIO, AIO, mmap I/O and splice I/O
> > on the same files.
> 
> Hi Eryu,
> 
> Great! Thanks for turning it into a test. Couple of comments
> below.
....
> > + +seq=`basename $0` +seqres=$RESULT_DIR/$seq +echo "QA output
> > created by $seq" + +here=`pwd` +tmp=/tmp/$$
> 
> Not a big deal, but using mktemp woud probably be better.

Not better at all - this reduces the easy of debugging problems.
e.g.  if a test is hung, I know where it's temporary output files
are just by looking at the process listing and grabbing the pid of
the test process being run. IOWs, we *want* deterministic temporary
filenames here - obscuring the temporary file names that tests use
doesn't gain us anything.

Yes, I see that some btrfs tests have used mktemp  and a couple of
generic tests use $TEST_DIR/$$ - they should be reverted to /tmp/$$
so they are consistent with the majority of tests and the new test
template....

Cheers,

Dave.
-- 
Dave Chinner
david@fromorbit.com

  parent reply	other threads:[~2015-06-09 22:27 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-08 10:41 [PATCH] generic: concurrent IO test with mixed IO types Eryu Guan
2015-06-08 11:02 ` Lukáš Czerner
2015-06-08 11:59   ` Eryu Guan
2015-06-08 12:36     ` Lukáš Czerner
2015-06-09 22:27   ` Dave Chinner [this message]
2015-06-08 12:41 ` [PATCH v2] " Eryu Guan
2015-06-09  8:39   ` Lukáš Czerner
2015-06-09 22:29   ` Dave Chinner
2015-06-10  7:07     ` Eryu Guan
2015-06-10 11:12       ` Dave Chinner
2015-06-10 11:37         ` Eryu Guan
2015-06-10  9:01     ` Lukáš Czerner
2015-06-10 11:11       ` Dave Chinner
2015-06-10 12:22         ` Lukáš Czerner
2015-06-10 13:59           ` Dave Chinner
2015-06-10 14:26             ` Lukáš Czerner
2015-06-11  9:17 ` [PATCH v3] " Eryu Guan
2015-06-17 22:15   ` Dave Chinner
2015-06-18  3:04     ` Eryu Guan
2015-06-18 23:31       ` Dave Chinner

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=20150609222709.GB24666@dastard \
    --to=david@fromorbit.com \
    --cc=eguan@redhat.com \
    --cc=fstests@vger.kernel.org \
    --cc=lczerner@redhat.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