Skip to content

mm/vmalloc: Assorted fixes and improvements

Thomas Gleixner linux-mm 2 versions – Applied

Status from this message: [merged mm-stable] mm-vmalloc-dont-purge-usable-blocks-unnecessarily.patch removed from -mm tree

Get series with b4
b4 am [email protected]

Versions newest first · linked by author and title

  1. v2 Latest6 patches 10 repliesApplied 6/6
  2. v16 patches 36 repliesSuperseded

Patches in v2 All 6 applied

#Subject and filesSizeRepliesApplied
1/6mm/vmalloc: Prevent stale TLBs in fully utilized blocksmm/vmalloc.c+2 -10 repliesApplied
2/6mm/vmalloc: Avoid iterating over per CPU vmap blocks twicemm/vmalloc.c+46 -242 repliesApplied
3/6mm/vmalloc: Prevent flushing dirty space over and overmm/vmalloc.c+6 -22 repliesApplied
4/6mm/vmalloc: Check free space in vmap_block locklessmm/vmalloc.c+4 -12 repliesApplied
5/6mm/vmalloc: Add missing READ/WRITE_ONCE() annotationsmm/vmalloc.c+8 -52 repliesApplied
6/6mm/vmalloc: Dont purge usable blocks unnecessarilymm/vmalloc.c+20 -81 replyApplied

Reviews trailers per patch

5 of 6 patches have a Reviewed-by or Acked-by of their own; the series has one for all of them.

PatchChristoph HellwigLorenzo StoakesUladzislau Rezki (Sony)Baoquan He
SeriesR-b
1/6R-b R-b R-b
2/6R-b R-b
3/6R-b R-b R-b
4/6R-b R-b R-b
5/6R-b R-b
6/6

Trailers given in replies are filled; those carried in the patches from earlier versions are outlined with dashes. Scroll the table sideways for all 4 reviewers.

Read the v2 thread

Cover letter [V2 patch 0/6] mm/vmalloc: Assorted fixes and improvements

This an update of version 1 which can be found here:

https://lore.kernel.org/mm/[email protected]

Following up to the discussion about excessive TLB flushes

https://lore.kernel.org/all/87a5y5a6kj.ffs@tglx

this series addresses the following issues:

1) Prevent the stale TLB problem related to fully utilized vmap blocks

2) Avoid the double per CPU list walk in _vm_unmap_aliases()

3) Avoid flushing dirty space over and over

4) Add a lockless quickcheck in vb_alloc() and add missing READ/WRITE_ONCE() annotations

5) Prevent overeager purging of usable vmap_blocks if not under memory/address space pressure.

Changes vs. version 1:

- Coding style issues
- Remove unneccesary force_purge arguments
- Amend changelog of 1/6
- Pick up Reviewed-by tags where applicable

Thanks,

tglx