space_seg_t should have its own kmem_cache
zfs - Zettabyte File System
From Matt Ahrens's original bug report at Delphix:
There are often many many entries in the loaded space_map's (~30,000 in each map, with dozens loaded). The space_seg_t's should have their own kmem_cache, so that we can easily monitor the amount of memory used. This will be especially important as we change the code to keep space maps loaded longer (or force them to stay loaded by setting metaslab_debug).
Updated by Christopher Siden over 8 years ago
- Status changed from In Progress to Closed
commit 01f55e48fb4d524eaf70687728aa51b7762e2e97 Author: George Wilson <firstname.lastname@example.org> Date: Wed Nov 7 14:05:17 2012 -0800 3329 spa_sync() spends 10-20% of its time in spa_free_sync_cb() 3330 space_seg_t should have its own kmem_cache 3331 deferred frees should happen after sync_pass 1 3335 make SYNC_PASS_* constants tunable Reviewed by: Adam Leventhal <email@example.com> Reviewed by: Matt Ahrens <firstname.lastname@example.org> Reviewed by: Christopher Siden <email@example.com> Reviewed by: Eric Schrock <firstname.lastname@example.org> Reviewed by: Richard Lowe <email@example.com> Reviewed by: Dan McDonald <firstname.lastname@example.org> Approved by: Eric Schrock <email@example.com>