From: M. Mohan Kumar <mohan@in.ibm.com>
To: lvm-devel@redhat.com
Subject: [PATCH V2 0/2] Add thin lv and thin pool creation support
Date: Fri, 01 Feb 2013 22:57:26 +0530 [thread overview]
Message-ID: <87mwvo0wsh.fsf@in.ibm.com> (raw)
In-Reply-To: <510BD450.1060801@redhat.com>
Tony Asleson <tasleson@redhat.com> writes:
> On 02/01/2013 12:08 AM, M. Mohan Kumar wrote:
>> Tony Asleson <tasleson@redhat.com> writes:
>>> One option would be to change the type to a signed integer and change
>>> the meaning from number of blocks free to percentage free and then treat
>>> -1 as pick a sane default. Thus 0 would be no events and 30 would
>>> indicate when 30% blocks free is remaining to generate an event. We
>>> could also use an unsigned value and use 100 as please pick a sane
>>> default as this value and values close to it really wouldn't make much
>>> sense.
>>
>> IMHO specifying the % in threshold is a good idea. You suggest to assume some
>> default threshold for newly created thin pool if user is not passing
>> anything. May be we can document this in lvm2app.h mentioning if '0'
>> passed as percentage it will be treated as the default thresold and 100%
>> means no event will be generated. What do you think about this policy?
>
> This would be fine too. As long as we clearly document what the value
> represents and what the special values which denote disable and select
> default we should be good.
>
> Do we know what a reasonable threshold value should be?
I am not sure about the threshold value, should it bring it to dm folks?
next prev parent reply other threads:[~2013-02-01 17:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-31 14:25 [PATCH V2 0/2] Add thin lv and thin pool creation support M. Mohan Kumar
2013-01-31 14:25 ` [PATCH V2 1/2] lvm2app: Add thin and thin pool lv creation M. Mohan Kumar
2013-01-31 14:25 ` [PATCH V2 2/2] master - thin: Add lowwatermark parameter to pool creation M. Mohan Kumar
2013-01-31 21:04 ` [PATCH V2 0/2] Add thin lv and thin pool creation support Tony Asleson
2013-01-31 21:35 ` Zdenek Kabelac
2013-02-01 5:36 ` M. Mohan Kumar
2013-02-01 6:08 ` M. Mohan Kumar
2013-02-01 14:42 ` Tony Asleson
2013-02-01 17:27 ` M. Mohan Kumar [this message]
2013-02-01 17:28 ` M. Mohan Kumar
2013-02-04 23:24 ` Tony Asleson
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=87mwvo0wsh.fsf@in.ibm.com \
--to=mohan@in.ibm.com \
--cc=lvm-devel@redhat.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 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.