mm, vmalloc: cleanup for vmap block
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest3 patches 3 repliesIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/3 | mm, vmalloc: Remove dead code in vb_allocmm/ | +1 | 0 replies | |
| 2/3 | mm, vmalloc: Remove unused purge_fragmented_blocks_thiscpumm/ | +0 | 0 replies | |
| 3/3 | mm, vmalloc: Remove alloc_map from vmap_blockmm/ | +0 | 0 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [PATCH 0/3] mm, vmalloc: cleanup for vmap block
This patchset is a cleanup for vmap block. And similar/same patches has been submitted before:
- Johannes Weiner's patch: https://lkml.org/lkml/2011/4/14/619
- Chanho Min's patch: https://lkml.org/lkml/2013/2/6/810
In Johannes's thread, Mel suggested to figure out if this bitmap was not supposed to be doing something useful and depending on that implement recycling of partially used vmap blocks.
Anyway, just as Johannes said, we shouldn't leave these dead/unused code as is, because it really is a waste of time for cpus and readers of the code. And this cleanup doesn't prevent anyone from improving the algorithm later on.
Based on the two patches before, I split the cleanup into three small pieces that may be more clear.
Zhang Yanfei (3):
mm, vmalloc: Remove dead code in vb_alloc
mm, vmalloc: Remove unused purge_fragmented_blocks_thiscpu mm, vmalloc: Remove alloc_map from vmap_block
mm/vmalloc.c | 24 +----------------------- 1 files changed, 1 insertions(+), 23 deletions(-)
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to [email protected]. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"[email protected]"> [email protected] </a>