From: Anand Jain <anand.jain@oracle.com>
To: Eryu Guan <eguan@redhat.com>
Cc: fstests@vger.kernel.org, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH v2 1/6] fstests: btrfs: add functions to set and reset required number of SCRATCH_DEV_POOL
Date: Wed, 22 Jun 2016 19:01:45 +0800 [thread overview]
Message-ID: <f69d7709-eec2-a0aa-c4d5-8f19a4251c04@oracle.com> (raw)
In-Reply-To: <20160621132030.GX5140@eguan.usersys.redhat.com>
On 06/21/2016 09:20 PM, Eryu Guan wrote:
> On Wed, Jun 15, 2016 at 04:46:03PM +0800, Anand Jain wrote:
>> From: Anand Jain <Anand.Jain@oracle.com>
>>
>> This patch provides functions
>> _scratch_dev_pool_get()
>> _scratch_dev_pool_put()
>>
>> Which will help to set/reset SCRATCH_DEV_POOL with the required
>> number of devices. SCRATCH_DEV_POOL_SAVED will hold all the devices.
>>
>> Usage:
>> _scratch_dev_pool_get() <ndevs>
>> :: do stuff
>>
>> _scratch_dev_pool_put()
>>
>> Signed-off-by: Anand Jain <anand.jain@oracle.com>
>
> I think the helpers should be introduced when they are first used, so
> that we know why they're introduced, and know how they're used with
> clear examples.
>
> So patch 1, 2 and 4 can be merged as one patch, patch 3 updates
> btrfs/027, patch 4 and patch 5 can be merged as one patch, then comes
> patch 6.
>
> What do you think?
Hm. I won't bother much on that. will do if needed.
(just a note- On the other hand it gets noticed about the
new helper function if its a separate patch for helper
function).
>> ---
>> v2: Error message and comment section updates.
>>
>> common/rc | 55 +++++++++++++++++++++++++++++++++++++++++++++++++++++++
>> 1 file changed, 55 insertions(+)
>>
>> diff --git a/common/rc b/common/rc
>> index 51092a0644f0..31c46ba1226e 100644
>> --- a/common/rc
>> +++ b/common/rc
>> @@ -802,6 +802,61 @@ _scratch_mkfs()
>> esac
>> }
>>
>> +#
>> +# Generally test cases will have..
>> +# _require_scratch_dev_pool X
>> +# to make sure it has the enough scratch devices including
>> +# replace-target and spare device. Now arg1 here is the
>> +# required number of scratch devices by a-test-case excluding
>> +# the replace-target and spare device. So this function will
>> +# set SCRATCH_DEV_POOL to the specified number of devices.
>> +#
>> +# Usage:
>> +# _scratch_dev_pool_get() <ndevs>
>> +# :: do stuff
>> +#
>> +# _scratch_dev_pool_put()
>> +#
>> +_scratch_dev_pool_get()
>> +{
>> + if [ $# != 1 ]; then
>
> "-ne" "-eq" etc. are used for comparing integers, "=!" "==" are for
> strings. And I think $#, $? are integers here, "-ne" would be better.
Thanks for the catch. fixed in next rev.
- Anand
> Thanks,
> Eryu
>
>> + _fail "Usage: _scratch_dev_pool_get ndevs"
>> + fi
>> +
>> + local test_ndevs=$1
>> + local config_ndevs=`echo $SCRATCH_DEV_POOL| wc -w`
>> + local devs[]="( $SCRATCH_DEV_POOL )"
>> +
>> + typeset -p config_ndevs >/dev/null 2>&1
>> + if [ $? != 0 ]; then
>> + _fail "Bug: cant find SCRATCH_DEV_POOL ndevs"
>> + fi
>> +
>> + if [ $config_ndevs -lt $test_ndevs ]; then
>> + _notrun "Need at least test requested number of ndevs $test_ndevs"
>> + fi
>> +
>> + SCRATCH_DEV_POOL_SAVED=${SCRATCH_DEV_POOL}
>> + export SCRATCH_DEV_POOL_SAVED
>> + SCRATCH_DEV_POOL=${devs[@]:0:$test_ndevs}
>> + export SCRATCH_DEV_POOL
>> +}
>> +
>> +_scratch_dev_pool_put()
>> +{
>> + typeset -p SCRATCH_DEV_POOL_SAVED >/dev/null 2>&1
>> + if [ $? != 0 ]; then
>> + _fail "Bug: unset val, must call _scratch_dev_pool_get before _scratch_dev_pool_put"
>> + fi
>> +
>> + if [ -z "$SCRATCH_DEV_POOL_SAVED" ]; then
>> + _fail "Bug: str empty, must call _scratch_dev_pool_get before _scratch_dev_pool_put"
>> + fi
>> +
>> + export SCRATCH_DEV_POOL=$SCRATCH_DEV_POOL_SAVED
>> + export SCRATCH_DEV_POOL_SAVED=""
>> +}
>> +
>> _scratch_pool_mkfs()
>> {
>> case $FSTYP in
>> --
>> 2.7.0
>>
>> --
>> To unsubscribe from this list: send the line "unsubscribe fstests" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
> --
> To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2016-06-22 11:01 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-17 14:32 [PATCH 1/6] fstests: btrfs: add functions to set and reset required number of SCRATCH_DEV_POOL Anand Jain
2016-05-17 14:32 ` [PATCH 2/6] fstests: btrfs: add functions to get and put a device for replace target Anand Jain
2016-06-12 4:42 ` Eryu Guan
2016-06-15 8:45 ` Anand Jain
2016-06-15 8:47 ` [PATCH v2 " Anand Jain
2016-05-17 14:32 ` [PATCH 3/6] fstests: btrfs: 027 make use of new device get and put helper functions Anand Jain
2016-05-17 14:32 ` [PATCH 4/6] fstests: btrfs: add helper function to check if btrfs is module Anand Jain
2016-06-12 4:53 ` Eryu Guan
2016-06-15 8:45 ` Anand Jain
2016-06-15 8:47 ` [PATCH v2 " Anand Jain
2016-05-17 14:32 ` [PATCH 5/6] fstests: btrfs: test RAID1 device reappear and balanced Anand Jain
2016-06-12 5:06 ` Eryu Guan
2016-06-15 8:45 ` Anand Jain
2016-06-15 8:48 ` [PATCH v2 " Anand Jain
2016-06-21 13:31 ` Eryu Guan
2016-06-22 11:01 ` Anand Jain
2016-06-27 9:29 ` Eryu Guan
2016-06-30 11:04 ` Anand Jain
2016-06-30 14:58 ` Eryu Guan
2016-06-23 13:28 ` [PATCH v3 2/6] fstests: btrfs: add functions to get and put a device for replace target Anand Jain
2016-06-30 10:58 ` [PATCH v3 5/6] fstests: btrfs: test RAID1 device reappear and balanced Anand Jain
2016-05-17 14:32 ` [PATCH 6/6] fstests: btrfs: test RAID5 device reappear and balance Anand Jain
2016-06-12 5:08 ` Eryu Guan
2016-06-15 8:51 ` Anand Jain
2016-06-15 8:49 ` [PATCH v2 " Anand Jain
2016-06-30 10:59 ` [PATCH v3 " Anand Jain
2016-06-12 4:40 ` [PATCH 1/6] fstests: btrfs: add functions to set and reset required number of SCRATCH_DEV_POOL Eryu Guan
2016-06-15 8:44 ` Anand Jain
2016-06-15 8:46 ` [PATCH v2 " Anand Jain
2016-06-21 13:20 ` Eryu Guan
2016-06-22 11:01 ` Anand Jain [this message]
2016-06-23 13:25 ` [PATCH v3 " Anand Jain
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=f69d7709-eec2-a0aa-c4d5-8f19a4251c04@oracle.com \
--to=anand.jain@oracle.com \
--cc=eguan@redhat.com \
--cc=fstests@vger.kernel.org \
--cc=linux-btrfs@vger.kernel.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 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).