kmem_reap does one xcall per page
We see performance problems due to kmem_reap() of ZFS's zio buf caches. The kmem_reap() causes a lot of cross-calls to tear down TLB entries, which is slow. It can also cause latency bubbles in concurrent zfs_read/zfs_write operations.
The problem is reliably triggered when a workload switches between accessing files of different blocksizes. This causes kmem to need to free lots of buffers of the old size in order to allocate ones of the new size.
We can improve on this in some cases by using one xcall per slab, to tear down all the virtually contiguous pages used to back the slab. The performance benefit will be most noticeable when reaping larger (e.g. 128KB) caches.
Updated by Electric Monk over 8 years ago
- Status changed from New to Closed
- % Done changed from 0 to 100
git commit a6a74e0e62d62ff750cd4b790be5eacc99c3bb8c
commit a6a74e0e62d62ff750cd4b790be5eacc99c3bb8c Author: Matthew Ahrens <firstname.lastname@example.org> Date: 2015-01-16T02:21:04.000Z 5498 kmem_reap does one xcall per page 5514 hat_unload_callback passes the wrong length to segvn_hat_unload_callback Reviewed by: Adam Leventhal <email@example.com> Reviewed by: Dan Kimmel <firstname.lastname@example.org> Reviewed by: George Wilson <email@example.com> Reviewed by: Josef 'Jeff' Sipek <firstname.lastname@example.org> Reviewed by: Paul Dagnelie <email@example.com> Reviewed by: Robert Mustacchi <firstname.lastname@example.org> Approved by: Richard Lowe <email@example.com>