From: Christoph Hellwig <hch@infradead.org>
To: Johannes Thumshirn <jthumshirn@suse.de>
Cc: Chaitanya Kulkarni <Chaitanya.Kulkarni@wdc.com>,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
"linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>,
"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
"linux-ide@vger.kernel.org" <linux-ide@vger.kernel.org>,
"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
"lsf-pc@lists.linux-foundation.org"
<lsf-pc@lists.linux-foundation.org>
Subject: Re: [LFS/MM TOPIC][LFS/MM ATTEND]: - Storage Stack and Driver Testing methodology.
Date: Wed, 11 Jan 2017 01:24:47 -0800 [thread overview]
Message-ID: <20170111092447.GA13600@infradead.org> (raw)
In-Reply-To: <20170111091945.GD6286@linux-x5ow.site>
On Wed, Jan 11, 2017 at 10:19:45AM +0100, Johannes Thumshirn wrote:
> Well, something I was thinking about but didn't find enough time to actually
> implement is making a xfstestes like test suite written using sg3_utils for
> SCSI.
Ronnie's libiscsi testsuite can use SG_IO for a new years now:
https://github.com/sahlberg/libiscsi/tree/master/test-tool
and has been very useful to find bus in various protocol
implementations.
> This idea could very well be extented to NVMe
Chaitanya suite is doing something similar for NVMe, although the
coverage is still much more limited so far.
WARNING: multiple messages have this Message-ID (diff)
From: hch@infradead.org (Christoph Hellwig)
Subject: [LFS/MM TOPIC][LFS/MM ATTEND]: - Storage Stack and Driver Testing methodology.
Date: Wed, 11 Jan 2017 01:24:47 -0800 [thread overview]
Message-ID: <20170111092447.GA13600@infradead.org> (raw)
In-Reply-To: <20170111091945.GD6286@linux-x5ow.site>
On Wed, Jan 11, 2017@10:19:45AM +0100, Johannes Thumshirn wrote:
> Well, something I was thinking about but didn't find enough time to actually
> implement is making a xfstestes like test suite written using sg3_utils for
> SCSI.
Ronnie's libiscsi testsuite can use SG_IO for a new years now:
https://github.com/sahlberg/libiscsi/tree/master/test-tool
and has been very useful to find bus in various protocol
implementations.
> This idea could very well be extented to NVMe
Chaitanya suite is doing something similar for NVMe, although the
coverage is still much more limited so far.
next prev parent reply other threads:[~2017-01-11 9:24 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CO2PR04MB218427BF42159B20FB26F74186670@CO2PR04MB2184.namprd04.prod.outlook.com>
2017-01-10 22:40 ` [LFS/MM TOPIC][LFS/MM ATTEND]: - Storage Stack and Driver Testing methodology Chaitanya Kulkarni
2017-01-10 22:40 ` Chaitanya Kulkarni
2017-01-10 22:40 ` Chaitanya Kulkarni
2017-01-11 7:42 ` Hannes Reinecke
2017-01-11 7:42 ` Hannes Reinecke
2017-01-11 7:42 ` Hannes Reinecke
2017-01-11 9:19 ` Johannes Thumshirn
2017-01-11 9:19 ` Johannes Thumshirn
2017-01-11 9:19 ` Johannes Thumshirn
2017-01-11 9:24 ` Christoph Hellwig [this message]
2017-01-11 9:24 ` Christoph Hellwig
2017-01-11 9:40 ` Hannes Reinecke
2017-01-11 9:40 ` Hannes Reinecke
2017-01-11 9:40 ` Hannes Reinecke
2017-03-10 19:37 ` Bart Van Assche
2017-03-10 19:37 ` Bart Van Assche
2017-03-10 19:37 ` Bart Van Assche
2017-01-12 11:01 ` [Lsf-pc] " Sagi Grimberg
2017-01-12 11:01 ` Sagi Grimberg
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=20170111092447.GA13600@infradead.org \
--to=hch@infradead.org \
--cc=Chaitanya.Kulkarni@wdc.com \
--cc=jthumshirn@suse.de \
--cc=linux-block@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=linux-scsi@vger.kernel.org \
--cc=lsf-pc@lists.linux-foundation.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.