lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Fri, 23 Jan 2015 12:03:53 -0500 From: Johannes Weiner <hannes@...xchg.org> To: Tejun Heo <tj@...nel.org> Cc: Michal Hocko <mhocko@...e.cz>, Andrew Morton <akpm@...ux-foundation.org>, Vladimir Davydov <vdavydov@...allels.com>, Greg Thelen <gthelen@...gle.com>, "linux-mm@...ck.org" <linux-mm@...ck.org>, Cgroups <cgroups@...r.kernel.org>, lkml <linux-kernel@...r.kernel.org> Subject: Re: [patch] mm: memcontrol: default hierarchy interface for memory fix - "none" On Tue, Jan 20, 2015 at 12:00:11PM -0500, Tejun Heo wrote: > Hello, > > On Tue, Jan 20, 2015 at 9:36 AM, Michal Hocko <mhocko@...e.cz> wrote: > > On Tue 20-01-15 09:30:02, Johannes Weiner wrote: > > [...] > >> Another possibility would be "infinity", > > > > yes infinity definitely sounds much better to me. > > FWIW, I prefer "max". It's shorter and clear enough. I don't think > there's anything ambiguous about "the memory max limit is at its > maximum". No need to introduce a different term. While I don't feel too strongly, I do agree with this. I don't see much potential for confusion, and "max" is much shorter and sweeter. Michal? -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists