diff options
| author | Lennart Poettering <lennart@poettering.net> | 2021-02-17 17:51:27 +0100 |
|---|---|---|
| committer | Lennart Poettering <lennart@poettering.net> | 2021-02-18 22:39:37 +0100 |
| commit | d9d3f05def0057cc064a05f8cbfb5f398779cd8c (patch) | |
| tree | c0f9a610b20970ccd122bf1d373334792d0a1bd4 /src/core/core-varlink.c | |
| parent | parse-util: add format string macro for outputting permyriad (diff) | |
| download | systemd-d9d3f05def0057cc064a05f8cbfb5f398779cd8c.tar.xz systemd-d9d3f05def0057cc064a05f8cbfb5f398779cd8c.zip | |
core: use our usual UINT32_MAX scaling for OOMD limits
So far OOMD limits used permyriads, as an upgrade from the original
percent.
The rest of our codebase typically scales stuff relative to UINT32_MAX.
Let's clean this up, an make sure this happens here too. This is
particularly relevant, as this is exposed in unit files and API, and
before we mark this stable we should get the APIs right.
Diffstat (limited to 'src/core/core-varlink.c')
| -rw-r--r-- | src/core/core-varlink.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/src/core/core-varlink.c b/src/core/core-varlink.c index df542e82d1..d695106658 100644 --- a/src/core/core-varlink.c +++ b/src/core/core-varlink.c @@ -83,7 +83,7 @@ static int build_managed_oom_json_array_element(Unit *u, const char *property, J JSON_BUILD_PAIR("mode", JSON_BUILD_STRING(mode)), JSON_BUILD_PAIR("path", JSON_BUILD_STRING(u->cgroup_path)), JSON_BUILD_PAIR("property", JSON_BUILD_STRING(property)), - JSON_BUILD_PAIR_CONDITION(use_limit, "limit", JSON_BUILD_UNSIGNED(c->moom_mem_pressure_limit_permyriad)))); + JSON_BUILD_PAIR_CONDITION(use_limit, "limit", JSON_BUILD_UNSIGNED(c->moom_mem_pressure_limit)))); } int manager_varlink_send_managed_oom_update(Unit *u) { |