LKML Archive on lore.kernel.org help / color / mirror / Atom feed
From: Michal Hocko <mhocko@suse.cz> To: Andrew Morton <akpm@linux-foundation.org> Cc: Johannes Weiner <hannes@cmpxchg.org>, Dave Chinner <david@fromorbit.com>, Mel Gorman <mgorman@suse.de>, Rik van Riel <riel@redhat.com>, Wu Fengguang <fengguang.wu@intel.com>, <linux-mm@kvack.org>, LKML <linux-kernel@vger.kernel.org>, Linux API <linux-api@vger.kernel.org> Subject: [PATCH 0/2] Move away from non-failing small allocations Date: Wed, 11 Mar 2015 16:54:52 -0400 [thread overview] Message-ID: <1426107294-21551-1-git-send-email-mhocko@suse.cz> (raw) Hi, as per discussion at LSF/MM summit few days back it seems there is a general agreement on moving away from "small allocations do not fail" concept. There are two patches in this series. The first one exports a sysctl knob which controls how hard small allocation (!__GFP_NOFAIL ones of course) retry when we get completely out of memory before the allocation fails. The default is still retry infinitely because we cannot simply change the 14+ years behavior right away. It will take years before all the potential fallouts are discovered and fixed and we can change the default value. The second patch is the first step in the transition plan. It changes the default but it is NOT an upstream material. It is aimed for brave testers who can cope with failures. I have talked to Andrew and he was willing to keep that patch in mmotm tree. It would be even better to have this in linux-next because the testing coverage would be even bigger. Dave Chinner has also shown an interest to integrate this into his xfstest farm. It would be great if Fenguang could add it into the zero testing project too (if the pushing the patch into linux-next would be too controversial).
next reply other threads:[~2015-03-11 20:55 UTC|newest] Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-03-11 20:54 Michal Hocko [this message] 2015-03-11 20:54 ` [PATCH 1/2] mm: Allow small allocations to fail Michal Hocko 2015-03-12 12:54 ` Tetsuo Handa 2015-03-12 13:12 ` Michal Hocko 2015-03-15 5:43 ` Tetsuo Handa 2015-03-15 12:13 ` Michal Hocko 2015-03-15 13:06 ` Tetsuo Handa 2015-03-16 7:46 ` [PATCH 1/2 v2] " Michal Hocko 2015-03-16 21:11 ` Johannes Weiner 2015-03-17 10:25 ` Michal Hocko 2015-03-17 13:29 ` Johannes Weiner 2015-03-17 14:17 ` Michal Hocko 2015-03-17 17:26 ` Johannes Weiner 2015-03-17 19:41 ` Michal Hocko 2015-03-18 9:10 ` Vlastimil Babka 2015-03-18 12:04 ` Michal Hocko 2015-03-18 12:36 ` Tetsuo Handa 2015-03-18 11:35 ` Tetsuo Handa 2015-03-17 11:13 ` Tetsuo Handa 2015-03-17 13:15 ` Michal Hocko 2015-03-18 11:33 ` Tetsuo Handa 2015-03-18 12:23 ` Michal Hocko 2015-03-19 11:03 ` Tetsuo Handa 2015-03-11 20:54 ` [PATCH 2/2] mmotm: Enable small allocation " Michal Hocko 2015-03-11 22:36 ` [PATCH 0/2] Move away from non-failing small allocations Sasha Levin 2015-03-16 22:38 ` Andrew Morton 2015-03-17 9:07 ` Michal Hocko 2015-03-17 14:06 ` Tetsuo Handa 2015-04-02 11:53 ` Tetsuo Handa
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=1426107294-21551-1-git-send-email-mhocko@suse.cz \ --to=mhocko@suse.cz \ --cc=akpm@linux-foundation.org \ --cc=david@fromorbit.com \ --cc=fengguang.wu@intel.com \ --cc=hannes@cmpxchg.org \ --cc=linux-api@vger.kernel.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-mm@kvack.org \ --cc=mgorman@suse.de \ --cc=riel@redhat.com \ /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: linkBe 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).