From: Masayoshi Mizuma <msys.mizuma@gmail.com>
To: vishal.l.verma@intel.com, linux-nvdimm@lists.01.org
Cc: m.mizuma@jp.fujitsu.com
Subject: Re: [PATCH v2] ndctl, test: add a new unit test for max_available_extent namespace
Date: Mon, 6 Aug 2018 08:59:56 -0400 [thread overview]
Message-ID: <2ed0a001-7edb-87a9-aa7c-cebed87e0684@gmail.com> (raw)
In-Reply-To: <1533332112.8557.98.camel@intel.com>
Hi Vishal,
Thank you for your review! I'll fix and send v3.
Thanks,
Masa
On 08/03/2018 05:35 PM, Verma, Vishal L wrote:
>
> On Fri, 2018-08-03 at 14:52 -0400, Masayoshi Mizuma wrote:
>> From: Masayoshi Mizuma <m.mizuma@jp.fujitsu.com>
>>
>> Add a new unit test to test max_available_extent namespace.
>> This feature is implemented by the following patches.
>>
>> kernel side:
>> https://lists.01.org/pipermail/linux-nvdimm/2018-July/016731.html
>> https://lists.01.org/pipermail/linux-nvdimm/2018-July/016732.html
>>
>> ndctl side:
>> https://lists.01.org/pipermail/linux-nvdimm/2018-July/017176.html
>>
>> Signed-off-by: Masayoshi Mizuma <m.mizuma@jp.fujitsu.com>
>> ---
>> test/Makefile.am | 3 ++-
>> test/max_available_extent_ns.sh | 43 +++++++++++++++++++++++++++++++++
>> 2 files changed, 45 insertions(+), 1 deletion(-)
>> create mode 100755 test/max_available_extent_ns.sh
>>
>> diff --git a/test/Makefile.am b/test/Makefile.am
>> index 8c55056..9af2464 100644
>> --- a/test/Makefile.am
>> +++ b/test/Makefile.am
>> @@ -22,7 +22,8 @@ TESTS =\
>> firmware-update.sh \
>> ack-shutdown-count-set \
>> rescan-partitions.sh \
>> - monitor.sh
>> + monitor.sh \
>> + max_available_extent_ns.sh
>>
>> check_PROGRAMS =\
>> libndctl \
>> diff --git a/test/max_available_extent_ns.sh b/test/max_available_extent_ns.sh
>> new file mode 100755
>> index 0000000..beea3bd
>> --- /dev/null
>> +++ b/test/max_available_extent_ns.sh
>> @@ -0,0 +1,43 @@
>> +#!/bin/bash -Ex
>> +
>> +# SPDX-License-Identifier: GPL-2.0
>> +# Copyright(c) 2018, FUJITSU LIMITED. All rights reserved.
>> +
>> +rc=77
>> +
>> +. ./common
>> +
>> +trap 'err $LINENO' ERR
>> +
>> +check_min_kver "4.19" || do_skip "kernel $KVER may not support max_available_size"
>> +
>> +init()
>> +{
>> + $NDCTL disable-region -b $NFIT_TEST_BUS0 all
>> + $NDCTL zero-labels -b $NFIT_TEST_BUS0 all
>> + $NDCTL enable-region -b $NFIT_TEST_BUS0 all
>> +}
>> +
>> +do_test()
>> +{
>> + region=$($NDCTL list -b $NFIT_TEST_BUS0 -R -t pmem | jq -r .[].dev | head -1)
>
> On my test setup, this fails because the region returned is the 32M
> one. This causes the namespaces requested to be 8M sized, which is too
> small, and hence rejected (16M minimum).
>
> The following jq query sorts it in descending size order and lets it
> choose the 64M region:
>
> jq -r 'sort_by(-.size) | .[].dev'
>
>> +
>> + available_sz=$($NDCTL list -r $region | jq -r .[].available_size)
>> + size=$(( available_sz/4 ))
>> +
>> + NS1=$($NDCTL create-namespace -r $region -t pmem -s $size | jq -r .dev)
>> + NS2=$($NDCTL create-namespace -r $region -t pmem -s $size | jq -r .dev)
>> + NS3=$($NDCTL create-namespace -r $region -t pmem -s $size | jq -r .dev)
>
> Since these happen in a subshell, errors are lost.
> Running in a subshell is fine, but we should test that the variables
> weren't blank:
>
> test -n "$NS1"
>
> And so on.
>
>> +
>> + $NDCTL disable-namespace $NS2
>> + $NDCTL destroy-namespace $NS2
>> +
>> + $NDCTL create-namespace -r $region -t pmem
>> +}
>> +
>> +modprobe nfit_test
>> +rc=1
>> +init
>> +do_test
>> +_cleanup
>> +exit 0
_______________________________________________
Linux-nvdimm mailing list
Linux-nvdimm@lists.01.org
https://lists.01.org/mailman/listinfo/linux-nvdimm
prev parent reply other threads:[~2018-08-06 12:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-03 18:52 [PATCH v2] ndctl, test: add a new unit test for max_available_extent namespace Masayoshi Mizuma
2018-08-03 21:35 ` Verma, Vishal L
2018-08-06 12:59 ` Masayoshi Mizuma [this message]
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=2ed0a001-7edb-87a9-aa7c-cebed87e0684@gmail.com \
--to=msys.mizuma@gmail.com \
--cc=linux-nvdimm@lists.01.org \
--cc=m.mizuma@jp.fujitsu.com \
--cc=vishal.l.verma@intel.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).