Re: [PATCH v4 1/3] mm/vmap: keep track of free blocks for vmap allocation

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

To: "Uladzislau Rezki (Sony)" <urezki@xxxxxxxxx>
Subject: Re: [PATCH v4 1/3] mm/vmap: keep track of free blocks for vmap allocation
From: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
Date: Tue, 14 May 2019 14:19:42 -0700
Cc: Roman Gushchin <guro@xxxxxx>, Michal Hocko <mhocko@xxxxxxxx>, Matthew Wilcox <willy@xxxxxxxxxxxxx>, linux-mm@xxxxxxxxx, LKML <linux-kernel@xxxxxxxxxxxxxxx>, Thomas Garnier <thgarnie@xxxxxxxxxx>, Oleksiy Avramchenko <oleksiy.avramchenko@xxxxxxxxxxxxxx>, Steven Rostedt <rostedt@xxxxxxxxxxx>, Joel Fernandes <joelaf@xxxxxxxxxx>, Thomas Gleixner <tglx@xxxxxxxxxxxxx>, Ingo Molnar <mingo@xxxxxxx>, Tejun Heo <tj@xxxxxxxxxx>
In-reply-to: <20190406183508.25273-2-urezki@gmail.com>
References: <20190406183508.25273-1-urezki@gmail.com> <20190406183508.25273-2-urezki@gmail.com>

An earlier version of this patch was accused of crashing the kernel:

https://lists.01.org/pipermail/lkp/2019-April/010004.html

does the v4 series address this?

Follow-Ups:
- Re: [PATCH v4 1/3] mm/vmap: keep track of free blocks for vmap allocation
  - From: Uladzislau Rezki

References:
- [PATCH v4 0/3] improve vmap allocation
  - From: Uladzislau Rezki (Sony)
- [PATCH v4 1/3] mm/vmap: keep track of free blocks for vmap allocation
  - From: Uladzislau Rezki (Sony)

Prev by Date: Re: [PATCH v2 0/6] mm/devm_memremap_pages: Fix page release race
Next by Date: [PATCH v3 1/2] memcg, oom: no oom-kill for __GFP_RETRY_MAYFAIL
Previous by thread: Re: [PATCH v4 1/3] mm/vmap: keep track of free blocks for vmap allocation
Next by thread: Re: [PATCH v4 1/3] mm/vmap: keep track of free blocks for vmap allocation
Index(es):
- Date
- Thread

[Index of Archives] [Linux ARM Kernel] [Linux ARM] [Linux Omap] [Fedora ARM] [IETF Annouce] [Bugtraq] [Linux OMAP] [Linux MIPS] [eCos] [Asterisk Internet PBX] [Linux API]

Powered by Linux