[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20150714142404.30f6a2255f5bd72c5b332279@linux-foundation.org>
Date: Tue, 14 Jul 2015 14:24:04 -0700
From: Andrew Morton <akpm@...ux-foundation.org>
To: David Rientjes <rientjes@...gle.com>
Cc: Mikulas Patocka <mpatocka@...hat.com>,
Mike Snitzer <msnitzer@...hat.com>,
"Alasdair G. Kergon" <agk@...hat.com>,
Edward Thornber <thornber@...hat.com>,
Vivek Goyal <vgoyal@...hat.com>, linux-kernel@...r.kernel.org,
linux-mm@...ck.org, dm-devel@...hat.com,
Linus Torvalds <torvalds@...ux-foundation.org>
Subject: Re: [PATCH 2/7] mm: introduce kvmalloc and kvmalloc_node
On Tue, 14 Jul 2015 14:13:16 -0700 (PDT) David Rientjes <rientjes@...gle.com> wrote:
> There's a misunderstanding in regards to the comment: __GFP_NORETRY
> doesn't turn direct reclaim or compaction off, it is still attempted and
> with the same priority as any other allocation. This only stops the page
> allocator from calling the oom killer, which will free memory or panic the
> system, and looping when memory is available.
include/linux/gfp.h says
* __GFP_NORETRY: The VM implementation must not retry indefinitely.
Can you suggest something more accurate and complete which we can put there?
--
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