From: Zdenek Kabelac <zkabelac@redhat.com>
To: lvm-devel@redhat.com
Subject: [PATCH] Fix RHBZ 754198 (multiple dmeventd snapshot extensions)
Date: Wed, 16 Nov 2011 10:44:02 +0100 [thread overview]
Message-ID: <4EC385E2.1000105@redhat.com> (raw)
In-Reply-To: <87ipmkxvlt.fsf@aldalome.int.mornfall.net.>
Dne 16.11.2011 10:30, Petr Rockai napsal(a):
> Alasdair G Kergon<agk@redhat.com> writes:
>> - real problem is the *calculation* must be going wrong if one
>> extend is insufficient to solve the problem!
>
> No, the real problem is that the snapshot is being filled and reaches
> the threshold again, after first extension is done. Nothing wrong with
> calculation.
Calculation should happen per every 5% increase.
Yet the logic there is IMHO not the best abd I'd say there are couple things
to improve.
Recalc is made on every 5% increase and 10 second delay is relatively
way too long time - when you could easily write over 100MB/s these days even
on very low level laptops - and better hardware may easily reach over 400MB/s
(We already have reports from users, which needed to use very low watermark
level to catch fast writing apps overfilling snapshot)
I'm playing with something similar on thinp support,
and I think we need something smarted here - which works with relative sizes
(well thinp will sleep at least - why not making the same for snapshots ?)
Anyway - related to Petr's patch - I don't like value '6' -
I would put there i.e. 128 - so we could keep real errors sequential within 7
bits ? and non-real-errors either 0 or > 127 (will we need more of these ?)
Zdenek
next prev parent reply other threads:[~2011-11-16 9:44 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 [this message]
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
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=4EC385E2.1000105@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.