throttle: Set always an average value when setting a maximum value
commit6f9b6d57ae3cd8a5f82e06f79d22e7a591116b5b
authorAlberto Garcia <berto@igalia.com>
Thu, 18 Feb 2016 10:26:58 +0000 (18 12:26 +0200)
committerKevin Wolf <kwolf@redhat.com>
Mon, 22 Feb 2016 13:08:05 +0000 (22 14:08 +0100)
treea8dfcc76b81dbad772de99e1655f36b19abe061b
parent03ba36c83d136a9d039b56f0a834e65676b58c22
throttle: Set always an average value when setting a maximum value

When testing the ranges of valid values, set_cfg_value() creates
sometimes invalid throttling configurations by setting bucket.max
while leaving bucket.avg uninitialized.

While this doesn't break the current tests, it will as soon as
we unify all functions that check the validity of the throttling
configuration.

This patch ensures that the value of bucket.avg is valid when setting
bucket.max.

Signed-off-by: Alberto Garcia <berto@igalia.com>
Reviewed-by: Kevin Wolf <kwolf@redhat.com>
Reviewed-by: Stefan Hajnoczi <stefanha@redhat.com>
Signed-off-by: Kevin Wolf <kwolf@redhat.com>
tests/test-throttle.c