Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1727534
| From | Michal Hocko <mhocko@kernel.org> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [v7 2/5] mm, oom: cgroup-aware OOM killer |
| Date | 2017-09-06 16:20 +0200 |
| Message-ID | <umJlo-2UP-9@gated-at.bofh.it> (permalink) |
| References | (3 earlier) <umE2m-7tt-5@gated-at.bofh.it> <umE2m-7tt-3@gated-at.bofh.it> <umIz4-2mH-55@gated-at.bofh.it> <umIz4-2mH-53@gated-at.bofh.it> <umJlo-2UP-11@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On Wed 06-09-17 14:41:42, Roman Gushchin wrote: [...] > Although, I don't think the whole thing is useful without any way > to adjust the memcg selection, so we can't postpone if for too long. > Anyway, if you think it's a way to go forward, let's do it. I am not really sure we are in a rush here. The whole oom_score_adj fiasco has showed that most users tend to only care "to never kill this and that". A better fine tuned oom control sounds useful at first but apart from very special usecases turns out very impractical to set up. At least that is my experience. There are special cases of course but we should target general use first. Kill the whole memcg is a really useful feature on its own for proper container cleanup. -- Michal Hocko SUSE Labs
Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Re: [v7 2/5] mm, oom: cgroup-aware OOM killer Michal Hocko <mhocko@kernel.org> - 2017-09-05 17:00 +0200
Re: [v7 2/5] mm, oom: cgroup-aware OOM killer Michal Hocko <mhocko@kernel.org> - 2017-09-06 10:40 +0200
Re: [v7 2/5] mm, oom: cgroup-aware OOM killer Michal Hocko <mhocko@kernel.org> - 2017-09-06 15:30 +0200
Re: [v7 2/5] mm, oom: cgroup-aware OOM killer Michal Hocko <mhocko@kernel.org> - 2017-09-06 16:20 +0200
Re: [v7 2/5] mm, oom: cgroup-aware OOM killer Michal Hocko <mhocko@kernel.org> - 2017-09-06 10:40 +0200
csiph-web