[dm-devel] Re: dm-userspace memory consumption in remap cache

[Dan Smith]

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 at us.ibm.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 190 bytes
Desc: not available
URL: <http://listman.redhat.com/archives/dm-devel/attachments/20060825/0d46f2fc/attachment.sig>