Hello, On Fri, Feb 14, 2020 at 04:13:18PM +0100, Michal Hocko wrote: > On Fri 14-02-20 08:57:28, Tejun Heo wrote: > > But that doesn't work for other controllers at all. I'm having a > > difficult time imagining how making this one control mechanism work > > that way makes sense. Memory protection has to be configured together > > with IO protection to be actually effective. > > Please be more specific. If the protected workload is mostly in-memory, > I do not really see how IO controller is relevant. See the example of > the DB setup I've mentioned elsewhere. Most applications, even the ones which don't use explicit IOs much, don't have set memory footprint which is uniformly accessed and there needs to be some level of reclaim activity for the working set to be established and maintained. Without IO control, memory protection isn't enough in protecting the workload. Even if we narrow down the discussion to something like memcache which has fixed memory footprint with almost uniform access pattern, real world applications don't exist in vacuum - they compete on CPU, have to do logging, pulls in metric ton of libraries which implicitly accesses stuff and so on. If somebody else is pummeling the filesystem and there's no IO isolation set up, it'll stall noticeably every once in a while. > > As for cgroup hierarchy being unrelated to how controllers behave, it > > frankly reminds me of cgroup1 memcg flat hierarchy thing I'm not sure > > how that would actually work in terms of resource isolation. Also, I'm > > not sure how systemd forces such configurations and I'd think systemd > > folks would be happy to fix them if there are such problems. Is the > > point you're trying to make "because of systemd, we have to contort > > how memory controller behaves"? > > No, I am just saying and as explained in reply to Johannes, there are > practical cases where the cgroup hierarchy reflects organizational > structure as well. Oh I see. If cgroup hierarchy isn't set up for resource control, resource control not working well seems par for the course. I mean, no other controllers would work anyway, so I'm having a hard time to see what the point is. What we ultimately want is cgroup actually being useful for its primary purpose of resource control while supporting other organizational use cases and while the established usages aren't there yet I haven't seen anything fundamentally blocking that. Thanks. -- tejun
