[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <6260a8af-3166-94d3-9441-104d342ab7a1@gmail.com>
Date: Thu, 19 Apr 2018 09:25:48 -0700
From: Eric Dumazet <eric.dumazet@...il.com>
To: Mikulas Patocka <mpatocka@...hat.com>,
David Miller <davem@...emloft.net>,
Andrew Morton <akpm@...ux-foundation.org>, linux-mm@...ck.org
Cc: eric.dumazet@...il.com, edumazet@...gle.com,
bhutchings@...arflare.com, netdev@...r.kernel.org,
linux-kernel@...r.kernel.org, mst@...hat.com, jasowang@...hat.com,
virtualization@...ts.linux-foundation.org, dm-devel@...hat.com,
Vlastimil Babka <vbabka@...e.cz>
Subject: Re: [PATCH] kvmalloc: always use vmalloc if CONFIG_DEBUG_VM
On 04/19/2018 09:12 AM, Mikulas Patocka wrote:
>
>
> These bugs are hard to reproduce because vmalloc falls back to kmalloc
> only if memory is fragmented.
>
This sentence is wrong.
.... because kvmalloc() falls back to vmalloc() ...
Powered by blists - more mailing lists