7994ac1d85
When I see "test", I have to think three times what the return value
means. With "below" this is immediately clear. ratelimit_below(&limit)
sounds almost like English and is imho immediately obvious.
(I also considered ratelimit_ok, but this strongly implies that being under the
limit is somehow better. Most of the times this is true, but then we use the
ratelimit to detect triple-c-a-d, and "ok" doesn't fit so well there.)
C.f. a1bcaa07.
44 lines
828 B
C
44 lines
828 B
C
/* SPDX-License-Identifier: LGPL-2.1+ */
|
|
/***
|
|
This file is part of systemd.
|
|
|
|
Copyright 2010 Lennart Poettering
|
|
***/
|
|
|
|
#include <sys/time.h>
|
|
|
|
#include "macro.h"
|
|
#include "ratelimit.h"
|
|
|
|
/* Modelled after Linux' lib/ratelimit.c by Dave Young
|
|
* <hidave.darkstar@gmail.com>, which is licensed GPLv2. */
|
|
|
|
bool ratelimit_below(RateLimit *r) {
|
|
usec_t ts;
|
|
|
|
assert(r);
|
|
|
|
if (r->interval <= 0 || r->burst <= 0)
|
|
return true;
|
|
|
|
ts = now(CLOCK_MONOTONIC);
|
|
|
|
if (r->begin <= 0 ||
|
|
r->begin + r->interval < ts) {
|
|
r->begin = ts;
|
|
|
|
/* Reset counter */
|
|
r->num = 0;
|
|
goto good;
|
|
}
|
|
|
|
if (r->num < r->burst)
|
|
goto good;
|
|
|
|
return false;
|
|
|
|
good:
|
|
r->num++;
|
|
return true;
|
|
}
|