From: Krishna Kanth Reddy <krish.reddy@samsung.com>
To: Dmitry Fomichev <Dmitry.Fomichev@wdc.com>
Cc: "axboe@kernel.dk" <axboe@kernel.dk>,
"fio@vger.kernel.org" <fio@vger.kernel.org>,
Ankit Kumar <ankit.kumar@samsung.com>,
Damien Le Moal <Damien.LeMoal@wdc.com>,
Shinichiro Kawasaki <shinichiro.kawasaki@wdc.com>
Subject: Re: [PATCH 4/4] t/zbd: Add support to verify Zone Append command with libaio, io_uring IO engine tests
Date: Fri, 3 Jul 2020 14:16:18 +0530 [thread overview]
Message-ID: <20200703084618.GA27933@test-zns> (raw)
In-Reply-To: <MN2PR04MB5951416AEA2856F350725EF8E1920@MN2PR04MB5951.namprd04.prod.outlook.com>
[-- Attachment #1: Type: text/plain, Size: 4187 bytes --]
On Thu, Jun 25, 2020 at 06:44:19PM +0000, Dmitry Fomichev wrote:
>Will these tests succeed if t/zbd/test-zbd-support script is run against an SMR HDD?
>Since zoned HDDs don't support Zone Append, I would expect the i/o to fail.
>I think you need to check if this device is an NVMe drive and expect the i/o failure in
>the tests below if this is not the case.
>
>More inline...
>
No, these tests fail for SMR HDD.
We will modify the script to run these tests only for NVMe drives.
>> -----Original Message-----
>> From: fio-owner@vger.kernel.org <fio-owner@vger.kernel.org> On Behalf
>> Of Krishna Kanth Reddy
>> Sent: Thursday, June 25, 2020 1:39 PM
>> To: axboe@kernel.dk
>> Cc: fio@vger.kernel.org; Krishna Kanth Reddy <krish.reddy@samsung.com>;
>> Ankit Kumar <ankit.kumar@samsung.com>
>> Subject: [PATCH 4/4] t/zbd: Add support to verify Zone Append command
>> with libaio, io_uring IO engine tests
>>
>> Modify the test-zbd-support script to verify the Zone Append command
>> for NVMe Zoned Namespaces (ZNS) defined in NVM Express TP4053.
>> Added a new FIO option zone_append.
>> When zone_append option is enabled, the existing write path will
>> send Zone Append command with LBA offset as start of the Zone.
>>
>> Signed-off-by: Ankit Kumar <ankit.kumar@samsung.com>
>> ---
>> t/zbd/test-zbd-support | 48
>> ++++++++++++++++++++++++++++++++++++++++++++++++
>> 1 file changed, 48 insertions(+)
>>
>> diff --git a/t/zbd/test-zbd-support b/t/zbd/test-zbd-support
>> index 4001be3..ddade22 100755
>> --- a/t/zbd/test-zbd-support
>> +++ b/t/zbd/test-zbd-support
>> @@ -801,6 +801,54 @@ test48() {
>> >> "${logfile}.${test_number}" 2>&1 || return $?
>> }
>>
>> +# Zone append to sequential zones, libaio, 1 job, queue depth 1
>> +test49() {
>> + local i size
>> +
>> + size=$((4 * zone_size))
>> + run_fio_on_seq --ioengine=libaio --iodepth=1 --rw=write --
>> zone_append=1 \
>> + --bs="$(max $((zone_size / 64)) "$logical_block_size")"\
>> + --do_verify=1 --verify=md5 \
>> + >>"${logfile}.${test_number}" 2>&1 || return $?
>> + check_written $size || return $?
>> + check_read $size || return $?
>> +}
>> +
>> +# Random zone append to sequential zones, libaio, 8 jobs, queue depth 64
>> per job
>> +test50() {
>> + local size
>> +
>> + size=$((4 * zone_size))
>> + run_fio_on_seq --ioengine=libaio --iodepth=64 --rw=randwrite --bs=4K \
>> + --group_reporting=1 --numjobs=8 --zone_append=1 \
>> + >> "${logfile}.${test_number}" 2>&1 || return $?
>> + check_written $((size * 8)) || return $?
>> +}
>> +
>> +# Zone append to sequential zones, io_uring, 1 job, queue depth 1
>> +test51() {
>> + local i size
>> +
>> + size=$((4 * zone_size))
>> + run_fio_on_seq --ioengine=io_uring --iodepth=1 --rw=write --
>> zone_append=1 \
>> + --bs="$(max $((zone_size / 64)) "$logical_block_size")"\
>> + --do_verify=1 --verify=md5 \
>> + >>"${logfile}.${test_number}" 2>&1 || return $?
>> + check_written $size || return $?
>> + check_read $size || return $?
>> +}
>> +
>> +# Random zone append to sequential zones, io_uring, 8 jobs, queue depth
>> 64 per job
>> +test52() {
>> + local size
>> +
>> + size=$((4 * zone_size))
>
>Maybe try some different size? It is the same in all tests.
>
Sure, we will add different sizes for the tests.
>> + run_fio_on_seq --ioengine=io_uring --iodepth=64 --rw=randwrite --
>> bs=4K \
>
>All tests do 4K i/o, but maybe try to run with a different block size?
>It could be a good idea to add a test that will write with bs=ZASL(or MDTS).
>Yet another test issuing i/o with bs exceeding the maximum i/o size would
>be very useful.
>
Ok, this input is very helpful. We will implement the tests as per your
review comments.
>> + --group_reporting=1 --numjobs=8 --zone_append=1 \
>> + >> "${logfile}.${test_number}" 2>&1 || return $?
>> + check_written $((size * 8)) || return $?
>> +}
>> +
>> tests=()
>> dynamic_analyzer=()
>> reset_all_zones=
>> --
>> 2.7.4
>
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
next prev parent reply other threads:[~2020-07-03 8:46 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20200625174119epcas5p122a2197102fe336aa35fdea1273fd1b0@epcas5p1.samsung.com>
2020-06-25 17:38 ` [PATCH 0/4] v2 Patchset : Zone Append command support for NVMe Zoned Namespaces (ZNS) Krishna Kanth Reddy
2020-06-25 17:38 ` [PATCH 1/4] Add " Krishna Kanth Reddy
2020-06-26 5:33 ` Damien Le Moal
2020-07-03 17:17 ` Krishna Kanth Reddy
2020-06-26 5:50 ` Damien Le Moal
2020-07-03 16:50 ` Krishna Kanth Reddy
2020-06-25 17:38 ` [PATCH 2/4] libaio: support for Zone Append command Krishna Kanth Reddy
2020-06-26 5:38 ` Damien Le Moal
2020-07-03 10:47 ` Krishna Kanth Reddy
2020-06-25 17:38 ` [PATCH 3/4] iouring: " Krishna Kanth Reddy
2020-06-26 5:43 ` Damien Le Moal
2020-07-03 10:37 ` Krishna Kanth Reddy
2020-06-25 17:38 ` [PATCH 4/4] t/zbd: Add support to verify Zone Append command with libaio, io_uring IO engine tests Krishna Kanth Reddy
2020-06-25 18:44 ` Dmitry Fomichev
2020-07-03 8:46 ` Krishna Kanth Reddy [this message]
2020-06-26 5:45 ` Damien Le Moal
2020-07-03 9:09 ` Krishna Kanth Reddy
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=20200703084618.GA27933@test-zns \
--to=krish.reddy@samsung.com \
--cc=Damien.LeMoal@wdc.com \
--cc=Dmitry.Fomichev@wdc.com \
--cc=ankit.kumar@samsung.com \
--cc=axboe@kernel.dk \
--cc=fio@vger.kernel.org \
--cc=shinichiro.kawasaki@wdc.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