Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1657147 > unrolled thread
| Started by | Vladimir Davydov <vdavydov.dev@gmail.com> |
|---|---|
| First post | 2017-06-04 21:50 +0200 |
| Last post | 2017-06-04 21:50 +0200 |
| Articles | 1 — 1 participant |
Back to article view | Back to linux.kernel
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
Re: [RFC PATCH v2 5/7] mm, oom: introduce oom_score_adj for memory cgroups Vladimir Davydov <vdavydov.dev@gmail.com> - 2017-06-04 21:50 +0200
| From | Vladimir Davydov <vdavydov.dev@gmail.com> |
|---|---|
| Date | 2017-06-04 21:50 +0200 |
| Subject | Re: [RFC PATCH v2 5/7] mm, oom: introduce oom_score_adj for memory cgroups |
| Message-ID | <tOJHb-14z-7@gated-at.bofh.it> |
On Thu, Jun 01, 2017 at 07:35:13PM +0100, Roman Gushchin wrote: > Introduce a per-memory-cgroup oom_score_adj setting. > A read-write single value file which exits on non-root > cgroups. The default is "0". > > It will have a similar meaning to a per-process value, > available via /proc/<pid>/oom_score_adj. > Should be in a range [-1000, 1000]. IMHO OOM scoring (not only the user API, but the logic as well) should be introduced by a separate patch following the main one (#6) in the series. Rationale: we might want to commit the main patch right away, while postponing OOM scoring for later, because some people might find the API controversial and needing a further, deeper discussion.
Back to top | Article view | linux.kernel
csiph-web