Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1175560 > unrolled thread
| Started by | David Rientjes <rientjes@google.com> |
|---|---|
| First post | 2015-07-01 23:40 +0200 |
| Last post | 2015-07-01 23:40 +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: [patch 1/3] mm, oom: organize oom context into struct David Rientjes <rientjes@google.com> - 2015-07-01 23:40 +0200
| From | David Rientjes <rientjes@google.com> |
|---|---|
| Date | 2015-07-01 23:40 +0200 |
| Subject | Re: [patch 1/3] mm, oom: organize oom context into struct |
| Message-ID | <pHxTA-28A-3@gated-at.bofh.it> |
On Wed, 1 Jul 2015, Sergey Senozhatsky wrote: > On (06/30/15 15:46), David Rientjes wrote: > > > > There are essential elements to an oom context that are passed around to > > > > multiple functions. > > > > > > > > Organize these elements into a new struct, struct oom_context, that > > > > specifies the context for an oom condition. > > > > > > > > > > s/oom_context/oom_control/ ? > > > > > > > I think it would be confused with the existing memory.oom_control for > > memcg. > > > > Hello David, > > Sorry, I meant that in commit message you say > > :Organize these elements into a new struct, struct oom_context, that > :specifies the context for an oom condition. > > but define and use `struct oom_control' (not `struct oom_context') > Oh, point very well taken, thank you. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Back to top | Article view | linux.kernel
csiph-web