From: Zdenek Kabelac <zkabelac@redhat.com>
To: lvm-devel@redhat.com
Subject: [PATCH] Fix RHBZ 754198 (multiple dmeventd snapshot extensions)
Date: Fri, 18 Nov 2011 21:48:45 +0100 [thread overview]
Message-ID: <4EC6C4AD.9080702@redhat.com> (raw)
In-Reply-To: <87obw9w6vv.fsf@aldalome.int.mornfall.net.>
Dne 18.11.2011 20:46, Petr Rockai napsal(a):
> Zdenek Kabelac<zkabelac@redhat.com> writes:
>
>> The formula above should be placed inside lvresize
>> (_adjust_policy_params()).
>
> And still completely besides the point.
>
>>> The problem:
>>>
>>> - to check whether anything needs to happen, lvextend needs to be
>>> executed (this is *expensive*, even if it decides no action needs to
>>> happen)
>>>
>>> - if nothing needed to happen, we don't need to call lvextend until the
>>> utilisation has grown; *but* we don't know whether anything happened
>>> (without ENO_ACTION_NEEDED that is)
>>
>> But you still call dmeventd_lvm2_run() - which is the most expensive
>> operation here - so I do not exactly see what do you actually safe here
>> i.e. if the resize will not happen because according to policy it's not
>> yet needed - then I do not see any difference ?
>
> Well, what can I say. I have already tried to explain how this works
> (twice?), and it's also quite obvious from the code. Well, once more: we
> do *not* call dmeventd_lvm2_run *if* the last lvconvert decided that
> nothing needs to be done *and* the snapshot utilisation did not change
> (more than 5%).
>
> To implement that, we need to: 1) know that snapshot utilisation grew
> (we know this already in the existing code) and 2) that lvconvert did
> not change anything. We don't know 2 and wrongly assume that nothing
> changes, ever (that's the bug).
>
> Were we to assume every time that lvconvert might have changed
> something, we would have to call it *every time* (every 10 seconds).
>
> Is it clear now?
>
Well my assumption is:
while {
read percentage
if converted && current_percent < last_time_percent
last_time_percent = current_percent
converted = 0
else if current_percent >= (last_time_percent + 5%)
lvconvert
converted = 1
else
wait 10sec
}
Zdenek
next prev parent reply other threads:[~2011-11-18 20:48 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-15 22:00 [PATCH] Fix RHBZ 754198 (multiple dmeventd snapshot extensions) Petr Rockai
2011-11-15 22:23 ` Milan Broz
[not found] ` <20111116000020.GA3294@agk-dp.fab.redhat.com>
2011-11-16 9:30 ` Petr Rockai
2011-11-16 9:44 ` Zdenek Kabelac
2011-11-16 10:28 ` Alasdair G Kergon
2011-11-16 1:20 ` Alasdair G Kergon
2011-11-16 9:41 ` Petr Rockai
2011-11-16 10:59 ` Alasdair G Kergon
2011-11-16 13:07 ` Alasdair G Kergon
2011-11-18 9:52 ` Petr Rockai
2011-11-18 17:14 ` Zdenek Kabelac
2011-11-18 19:46 ` Petr Rockai
2011-11-18 19:56 ` Alasdair G Kergon
2011-11-18 20:28 ` Petr Rockai
2011-11-18 21:19 ` Petr Rockai
2011-11-18 20:48 ` Zdenek Kabelac [this message]
2011-11-18 20:53 ` Alasdair G Kergon
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=4EC6C4AD.9080702@redhat.com \
--to=zkabelac@redhat.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.