BG> In fact, when the dmu device is unmapped, destroy_dmu_device() BG> moves all of the dmu_maps to the end of the MRU list but does not BG> free them, so that memory stays around. If a new device is BG> created, its dmu_maps will still be obtained from kmem_cache_alloc BG> even though there are unused dmu_maps. Ah, yet another good point :) BG> Come to think of it, that would be very interesting data in its BG> own right. I agree. BG> ...I'm probably missing an obvious reason that that won't work. I'm not sure why it wouldn't work. I think it's likely to result in a lot of polling, but it could definitely be useful in certain situations. -- Dan Smith IBM Linux Technology Center Open Hypervisor Team email: danms@xxxxxxxxxx
Attachment:
pgpU7dKw1SiXK.pgp
Description: PGP signature
-- dm-devel mailing list dm-devel@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/dm-devel
