Messages in this thread | | | Date | Tue, 11 Aug 2020 19:36:26 +0200 | From | Michal Koutný <> | Subject | Re: [RFC PROPOSAL] memcg: per-memcg user space reclaim interface |
| |
Hi Shakeel.
On Tue, Jul 07, 2020 at 10:02:50AM -0700, Shakeel Butt <shakeelb@google.com> wrote: > > Well, I was talkingg about memory.low. It is not meant only to protect > > from the global reclaim. It can be used for balancing memory reclaim > > from _any_ external memory pressure source. So it is somehow related to > > the usecase you have mentioned. > > > > For the uswapd use-case, I am not concerned about the external memory > pressure source but the application hitting its own memory.high limit > and getting throttled. FTR, you can transform own memory.high into "external" pressure with a hierarchy such as
limit-group memory.high=N+margin memory.low=0 `- latency-sensitive-group memory.low=N `- regular-group memory.low=0
Would that ensure the latency targets?
Michal [unhandled content-type:application/pgp-signature] | |