From: Omar Sandoval <osandov@osandov.com>
To: James Wang <jnwang@suse.com>
Cc: osandov@fb.com, hch@infradead.org, axboe@fb.com, hare@suse.com,
linux-block@vger.kernel.org, linux-kernel@vger.kernel.org,
mgorman@suse.com
Subject: Re: [PATCH blktests v2] loop/002: Regression testing for loop device flush
Date: Fri, 18 Aug 2017 01:11:27 -0700 [thread overview]
Message-ID: <20170818081127.GJ2459@vader> (raw)
In-Reply-To: <20170627040147.8823-1-jnwang@suse.com>
On Tue, Jun 27, 2017 at 12:01:47PM +0800, James Wang wrote:
> Add a regression testing for loop device. when an unbound device
> be close that take too long time. kernel will consume serveral orders
> of magnitude more wall time than it does for a mounted device.
James, sorry I forgot about this. I ended up committing a simplified
version here:
https://github.com/osandov/blktests/commit/bbe69c4cc83ddc36e5c82114890ac071d01c8ac5
Thanks for the test!
next prev parent reply other threads:[~2017-08-18 8:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-27 4:01 [PATCH blktests v2] loop/002: Regression testing for loop device flush James Wang
2017-08-18 8:11 ` Omar Sandoval [this message]
2017-08-18 10:09 ` James Wang
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=20170818081127.GJ2459@vader \
--to=osandov@osandov.com \
--cc=axboe@fb.com \
--cc=hare@suse.com \
--cc=hch@infradead.org \
--cc=jnwang@suse.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mgorman@suse.com \
--cc=osandov@fb.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