How to control the device mapper 's memory use?(or the IO queue limits?)
I created a thin-lun using dm-thin module. When used the
'dd' cmd to write to the thin lun ( the memory of my server is 10G, dd
file size is 50G, thin lun size is 100G ), only 60M was free. Then I
used 'iostat' to see how many io the dm device blocked, the number was
more than 1,000,000. Does the device mapper limit the mapped device's
queue? If not, how can limit the memory use, if we use writ-back, more
and more io will be mapped to the thin target?
Is there any way to limit the mapped device 's request queue(or
it has been done)? I test the shared-snapshot(Mikulas), 'dd' the
origin volume(has snap volume ), big part of the memory will be used
and the IO number of the dm device is very big (use 'iostat').
Best Wishes & Regards,
dm-devel mailing list