linux-nvme.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Chaitanya Kulkarni <Chaitanya.Kulkarni@wdc.com>
To: "linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
	"linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>
Cc: Omar Sandoval <osandov@fb.com>
Subject: Re: [PATCH 0/5 blktest] nvme: add cntlid and model testcases
Date: Mon, 3 Feb 2020 22:48:29 +0000	[thread overview]
Message-ID: <BYAPR04MB5749FE36341AB61547C1218A86000@BYAPR04MB5749.namprd04.prod.outlook.com> (raw)
In-Reply-To: 20200129232921.11771-1-chaitanya.kulkarni@wdc.com

(+ Omar)

On 01/29/2020 03:29 PM, Chaitanya Kulkarni wrote:
> This is a small patch-series which adds two new testcases for
> setting up controller IDs and model from configfs.
>
> Regards,
> Chaitanya
>
>
> Chaitanya Kulkarni (5):
>    nvme: allow target subsys set cntlid min/max
>    nvme: test target cntlid min cntlid max
>    nvme: allow target subsys set model
>    nvme: test target model attribute
>    nvme: make new testcases backward compatible
>
>   tests/nvme/033     | 61 ++++++++++++++++++++++++++++++++++++++++++++
>   tests/nvme/033.out |  4 +++
>   tests/nvme/034     | 63 ++++++++++++++++++++++++++++++++++++++++++++++
>   tests/nvme/034.out |  3 +++
>   tests/nvme/rc      | 24 ++++++++++++++++++
>   5 files changed, 155 insertions(+)
>   create mode 100755 tests/nvme/033
>   create mode 100644 tests/nvme/033.out
>   create mode 100755 tests/nvme/034
>   create mode 100644 tests/nvme/034.out
>
> Test Log :-
>
> Without cntlid_min/max and model patches :-
>
> nvme/002 (create many subsystems and test discovery)         [passed]
>      runtime  15.246s  ...  15.053s
> nvme/003 (test if we're sending keep-alives to a discovery controller) [passed]
>      runtime  10.057s  ...  10.063s
> ./check: no group or test named nvme/0004
> nvme/005 (reset local loopback target)                       [not run]
>      nvme_core module does not have parameter multipath
> nvme/006 (create an NVMeOF target with a block device-backed ns) [passed]
>      runtime  0.057s  ...  0.065s
> nvme/007 (create an NVMeOF target with a file-backed ns)     [passed]
>      runtime  0.036s  ...  0.038s
> nvme/008 (create an NVMeOF host with a block device-backed ns) [passed]
>      runtime  1.233s  ...  1.240s
> nvme/009 (create an NVMeOF host with a file-backed ns)       [passed]
>      runtime  1.203s  ...  1.208s
> nvme/014 (flush a NVMeOF block device-backed ns)             [passed]
>      runtime  14.572s  ...  16.051s
> nvme/015 (unit test for NVMe flush for file backed ns)       [passed]
>      runtime  13.584s  ...  13.948s
> nvme/016 (create/delete many NVMeOF block device-backed ns and test discovery) [passed]
>      runtime  9.877s  ...  10.750s
> nvme/017 (create/delete many file-ns and test discovery)     [passed]
>      runtime  18.902s  ...  15.584s
> nvme/019 (test NVMe DSM Discard command on NVMeOF block-device ns) [passed]
>      runtime  1.217s  ...  1.237s
> nvme/020 (test NVMe DSM Discard command on NVMeOF file-backed ns) [passed]
>      runtime  1.204s  ...  1.193s
> nvme/021 (test NVMe list command on NVMeOF file-backed ns)   [passed]
>      runtime  1.204s  ...  1.195s
> nvme/022 (test NVMe reset command on NVMeOF file-backed ns)  [passed]
>      runtime    ...  1.334s
> nvme/023 (test NVMe smart-log command on NVMeOF block-device ns) [passed]
>      runtime  1.218s  ...  1.231s
> nvme/024 (test NVMe smart-log command on NVMeOF file-backed ns) [passed]
>      runtime  1.207s  ...  1.196s
> nvme/025 (test NVMe effects-log command on NVMeOF file-backed ns) [passed]
>      runtime  1.191s  ...  1.195s
> nvme/026 (test NVMe ns-descs command on NVMeOF file-backed ns) [passed]
>      runtime  1.192s  ...  1.196s
> nvme/027 (test NVMe ns-rescan command on NVMeOF file-backed ns) [passed]
>      runtime  1.211s  ...  1.191s
> nvme/028 (test NVMe list-subsys command on NVMeOF file-backed ns) [passed]
>      runtime  1.204s  ...  1.211s
> nvme/033 (Test NVMeOF target cntlid[min|max] attributes)     [not run]
>      attr_cntlid_[min|max] not found
> nvme/034 (Test NVMeOF target model attribute)                [not run]
>      attr_cntlid_model not found
>
> With cntlid_min/max and model patches :-
>
> nvme/002 (create many subsystems and test discovery)         [passed]
>      runtime  15.053s  ...  11.918s
> nvme/003 (test if we're sending keep-alives to a discovery controller) [passed]
>      runtime  10.063s  ...  10.058s
> ./check: no group or test named nvme/0004
> nvme/005 (reset local loopback target)                       [not run]
>      nvme_core module does not have parameter multipath
> nvme/006 (create an NVMeOF target with a block device-backed ns) [passed]
>      runtime  0.065s  ...  0.065s
> nvme/007 (create an NVMeOF target with a file-backed ns)     [passed]
>      runtime  0.038s  ...  0.036s
> nvme/008 (create an NVMeOF host with a block device-backed ns) [passed]
>      runtime  1.240s  ...  1.239s
> nvme/009 (create an NVMeOF host with a file-backed ns)       [passed]
>      runtime  1.208s  ...  1.207s
> nvme/014 (flush a NVMeOF block device-backed ns)             [passed]
>      runtime  16.051s  ...  15.345s
> nvme/015 (unit test for NVMe flush for file backed ns)       [passed]
>      runtime  13.948s  ...  13.977s
> nvme/016 (create/delete many NVMeOF block device-backed ns and test discovery) [passed]
>      runtime  10.750s  ...  9.698s
> nvme/017 (create/delete many file-ns and test discovery)     [passed]
>      runtime  15.584s  ...  15.514s
> nvme/019 (test NVMe DSM Discard command on NVMeOF block-device ns) [passed]
>      runtime  1.237s  ...  1.232s
> nvme/020 (test NVMe DSM Discard command on NVMeOF file-backed ns) [passed]
>      runtime  1.193s  ...  1.192s
> nvme/021 (test NVMe list command on NVMeOF file-backed ns)   [passed]
>      runtime  1.195s  ...  1.195s
> nvme/022 (test NVMe reset command on NVMeOF file-backed ns)  [passed]
>      runtime  1.334s  ...  1.340s
> nvme/023 (test NVMe smart-log command on NVMeOF block-device ns) [passed]
>      runtime  1.231s  ...  1.218s
> nvme/024 (test NVMe smart-log command on NVMeOF file-backed ns) [passed]
>      runtime  1.196s  ...  1.205s
> nvme/025 (test NVMe effects-log command on NVMeOF file-backed ns) [passed]
>      runtime  1.195s  ...  1.191s
> nvme/026 (test NVMe ns-descs command on NVMeOF file-backed ns) [passed]
>      runtime  1.196s  ...  1.186s
> nvme/027 (test NVMe ns-rescan command on NVMeOF file-backed ns) [passed]
>      runtime  1.191s  ...  1.192s
> nvme/028 (test NVMe list-subsys command on NVMeOF file-backed ns) [passed]
>      runtime  1.211s  ...  1.187s
> nvme/033 (Test NVMeOF target cntlid[min|max] attributes)     [passed]
>      runtime  1.213s  ...  1.200s
> nvme/034 (Test NVMeOF target model attribute)                [passed]
>      runtime  1.223s  ...  1.204s
>
>


_______________________________________________
linux-nvme mailing list
linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme

  parent reply	other threads:[~2020-02-03 22:48 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-29 23:29 [PATCH 0/5 blktest] nvme: add cntlid and model testcases Chaitanya Kulkarni
2020-01-29 23:29 ` [PATCH 1/5 blktests] nvme: allow target subsys set cntlid min/max Chaitanya Kulkarni
2020-02-11 21:50   ` Omar Sandoval
2020-01-29 23:29 ` [PATCH 2/5 blktests] nvme: test target cntlid min cntlid max Chaitanya Kulkarni
2020-02-11 21:58   ` Omar Sandoval
2020-01-29 23:29 ` [PATCH 3/5 blktests] nvme: allow target subsys set model Chaitanya Kulkarni
2020-02-11 22:00   ` Omar Sandoval
2020-02-14  0:58     ` Chaitanya Kulkarni
2020-02-14  1:11     ` Chaitanya Kulkarni
2020-01-29 23:29 ` [PATCH 4/5 blktests] nvme: test target model attribute Chaitanya Kulkarni
2020-02-11 22:04   ` Omar Sandoval
2020-01-29 23:29 ` [PATCH 5/5 blktests] nvme: make new testcases backward compatible Chaitanya Kulkarni
2020-02-11 22:06   ` Omar Sandoval
2020-02-11 22:18     ` Chaitanya Kulkarni
2020-02-03 22:48 ` Chaitanya Kulkarni [this message]
2020-02-11 16:46   ` [PATCH 0/5 blktest] nvme: add cntlid and model testcases Chaitanya Kulkarni
2020-02-11 22:07     ` Omar Sandoval
2020-02-11 22:17       ` Chaitanya Kulkarni

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=BYAPR04MB5749FE36341AB61547C1218A86000@BYAPR04MB5749.namprd04.prod.outlook.com \
    --to=chaitanya.kulkarni@wdc.com \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-nvme@lists.infradead.org \
    --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;
as well as URLs for NNTP newsgroup(s).