From: One Thousand Gnomes <gnomes@lxorguk.ukuu.org.uk>
To: Michal Hocko <mhocko@kernel.org>
Cc: Mason <slash.tmp@free.fr>, Sebastian Frias <sf84@laposte.net>,
linux-mm@kvack.org, Andrew Morton <akpm@linux-foundation.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] mm: add config option to select the initial overcommit mode
Date: Fri, 13 May 2016 16:04:10 +0100 [thread overview]
Message-ID: <20160513160410.10c6cea6@lxorguk.ukuu.org.uk> (raw)
In-Reply-To: <20160513140128.GQ20141@dhcp22.suse.cz>
> > Perhaps Sebastian's choice could be made to depend on CONFIG_EMBEDDED,
> > rather than CONFIG_EXPERT?
>
> Even if the overcommit behavior is different on those systems the
> primary question hasn't been answered yet. Why cannot this be done from
> the userspace? In other words what wouldn't work properly?
Most allocations in C have no mechanism to report failure.
Stakc expansion failure is not reportable. Copy on write failure is not
reportable and so on.
Alan
next prev parent reply other threads:[~2016-05-13 15:04 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-10 11:56 [PATCH] mm: add config option to select the initial overcommit mode Sebastian Frias
2016-05-10 12:00 ` Fwd: " Sebastian Frias
2016-05-10 12:39 ` Andy Whitcroft
2016-05-10 13:02 ` Sebastian Frias
2016-05-13 8:04 ` Michal Hocko
2016-05-13 8:44 ` Mason
2016-05-13 9:52 ` Michal Hocko
2016-05-13 10:18 ` Mason
2016-05-13 10:42 ` Sebastian Frias
2016-05-13 11:44 ` Michal Hocko
2016-05-13 12:15 ` Mason
2016-05-13 14:01 ` Michal Hocko
2016-05-13 14:15 ` Sebastian Frias
2016-05-13 15:04 ` One Thousand Gnomes [this message]
2016-05-13 15:37 ` Sebastian Frias
2016-05-13 15:43 ` One Thousand Gnomes
2016-05-17 8:24 ` Sebastian Frias
2016-05-17 8:57 ` Michal Hocko
2016-05-17 16:16 ` Sebastian Frias
2016-05-17 17:29 ` Austin S. Hemmelgarn
2016-05-18 15:19 ` Sebastian Frias
2016-05-18 16:28 ` Austin S. Hemmelgarn
2016-05-17 20:16 ` Michal Hocko
2016-05-18 15:18 ` Sebastian Frias
2016-05-19 7:14 ` Michal Hocko
2016-05-13 17:01 ` Austin S. Hemmelgarn
2016-05-13 13:27 ` Austin S. Hemmelgarn
2016-05-13 9:52 ` Sebastian Frias
2016-05-13 12:00 ` Michal Hocko
2016-05-13 12:39 ` Sebastian Frias
2016-05-13 13:11 ` Austin S. Hemmelgarn
2016-05-13 13:32 ` Sebastian Frias
2016-05-13 13:51 ` Austin S. Hemmelgarn
2016-05-13 14:35 ` Sebastian Frias
2016-05-13 14:54 ` Michal Hocko
2016-05-13 15:15 ` Austin S. Hemmelgarn
2016-05-13 13:34 ` Sebastian Frias
2016-05-13 14:14 ` Austin S. Hemmelgarn
2016-05-13 14:23 ` Sebastian Frias
2016-05-13 15:02 ` Austin S. Hemmelgarn
2016-05-13 15:01 ` One Thousand Gnomes
2016-05-13 15:15 ` Sebastian Frias
2016-05-13 15:25 ` Michal Hocko
2016-05-13 14:51 ` Michal Hocko
2016-05-13 14:59 ` Mason
2016-05-13 15:11 ` One Thousand Gnomes
2016-05-13 15:26 ` Michal Hocko
2016-05-13 15:32 ` Sebastian Frias
2016-05-13 15:10 ` Sebastian Frias
2016-05-13 15:41 ` One Thousand Gnomes
2016-05-23 13:11 ` Sebastian Frias
2016-05-17 9:03 ` Mason
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160513160410.10c6cea6@lxorguk.ukuu.org.uk \
--to=gnomes@lxorguk.ukuu.org.uk \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.org \
--cc=sf84@laposte.net \
--cc=slash.tmp@free.fr \
--cc=torvalds@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).