Rafal Wojtczuk 37e06d19e4 qmemman: handle requests for small pieces correctly ... There seems to be a problem with xm mem-set, when executed for a value very close to the current value - the request is ignored; apparently, the domU kernel imposes some granularity on the request size. So, if qmemman is asked for, say 470MB, and there is 469MB free, it will try to milk 1MB from all domains - and this will fail. REQ_SAFETY_NET_FACTOR does not help in this scenario. The logs show req= 1110016 avail= 2503727104.0 donors [('11', 194375270.40000001),... borrow 90484.1597129 from 11 - so, beg for 90K from a domain borrow 132239.288652 from 10 borrow 537099.316089 from 0 borrow 148004.024941 from 7 borrow 139834.21573 from 9 borrow 117855.794876 from 8 and then we fail when a domain does not provide this lousy 90KB. The solution is to ask for actual_need+XEN_FREE_MEM_LEFT, but return if we already have actual_need+XEN_FREE_MEM_MIN (the latter is 25MB smaller).		2011-04-05 10:52:53 +02:00
..
Makefile	Make 'make clean' clean all the object files	2010-09-15 15:36:04 +02:00
qmemman_algo.py	qmemman: do not trim the mem-set value too much	2010-09-16 16:40:09 +02:00
qmemman_client.py	qmemman: in client code, set FD_CLOEXEC on qmmemman.socket	2010-09-09 12:33:48 +02:00
qmemman_server.py	qmemman: trigger do_balance() on receiving /proc/meminfo data	2010-09-09 12:36:18 +02:00
qmemman.py	qmemman: handle requests for small pieces correctly	2011-04-05 10:52:53 +02:00
server.py	Memory management across VMs, first release	2010-08-30 11:40:19 +02:00