From: Omar Sandoval <osandov@osandov.com>
To: Ming Lei <ming.lei@redhat.com>
Cc: Omar Sandoval <osandov@fb.com>, linux-block@vger.kernel.org
Subject: Re: [PATCH V2] blktests: add userspace IO test
Date: Mon, 11 Mar 2019 13:55:05 -0700 [thread overview]
Message-ID: <20190311205505.GC1315@vader> (raw)
In-Reply-To: <20190305015026.10751-1-ming.lei@redhat.com>
On Tue, Mar 05, 2019 at 09:50:26AM +0800, Ming Lei wrote:
> Add one test to cover changes on block passthrough IO interface,
> such as blk_rq_map_user(), blk_rq_map_user_iov(), blk_rq_unmap_user()
> and blk_rq_map_kern().
>
> Signed-off-by: Ming Lei <ming.lei@redhat.com>
> ---
> tests/block/029 | 111 ++++++++++++++++++++++++++++++++++++++++++++++++++++
> tests/block/029.out | 4 ++
> 2 files changed, 115 insertions(+)
> create mode 100755 tests/block/029
> create mode 100644 tests/block/029.out
>
> diff --git a/tests/block/029 b/tests/block/029
> new file mode 100755
> index 000000000000..c7c674464285
> --- /dev/null
> +++ b/tests/block/029
> @@ -0,0 +1,111 @@
> +#!/bin/bash
> +# SPDX-License-Identifier: GPL-2.0+
> +# Copyright (c) 2019 Ming Lei <ming.lei@redhat.com>
> +#
> +# Test userspace IO on NVMe loop device
This is still missing a reference to the patch it's testing.
> +. tests/nvme/rc
Shouldn't this be in the nvme group?
> +DESCRIPTION="test userspace IO via nvme-cli read/write interface"
> +QUICK=1
> +
> +requires() {
> + _have_program nvme && _have_modules loop nvme-loop nvmet && \
> + _have_configfs
> +}
> +
> +__test_user_io()
> +{
> + local disk="$1"
> + local start=$2
> + local cnt=$3
> +
> + local bs=$(blockdev --getss $disk)
This still has a ton of missing quoting and shellcheck errors.
I fixed all of this and pushed to
https://github.com/osandov/blktests/tree/user-io. Let me know if this
looks fine and I'll push it to master.
next prev parent reply other threads:[~2019-03-11 20:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-05 1:50 [PATCH V2] blktests: add userspace IO test Ming Lei
2019-03-11 20:55 ` Omar Sandoval [this message]
2019-03-21 22:36 ` Omar Sandoval
2019-03-22 1:04 ` Ming Lei
2019-03-25 17:29 ` Omar Sandoval
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=20190311205505.GC1315@vader \
--to=osandov@osandov.com \
--cc=linux-block@vger.kernel.org \
--cc=ming.lei@redhat.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