Milan Broz 8e1d5615b4 Introduce memory pool per volume group. ... Since now, all code reading volume group is responsible for releasing the memory allocated by calling vg_release(vg). (For simplicity of use, vg_releae can be called for vg == NULL, the same logic like free(NULL)). Also providing simple macro for unlocking & releasing in one step, tools usualy uses this approach. The global memory pool (cmd->mem) should be used only for global physical volume operations. This patch have to be applied with all subsequent patches to complete memory pool per vg logic. Using separate memory pool has quite bit memory saving impact when using large VGs, this is mainly needed when we have to use preallocated and locked memory (and should not overflow from that memory space).		2009-04-10 09:59:18 +00:00
..
.exported_symbols	.export.sym generation	2004-03-26 14:51:23 +00:00
disk-rep.c	Right, a simple build (without options) is working again.	2008-11-03 22:14:30 +00:00
disk-rep.h	Right, a simple build (without options) is working again.	2008-11-03 22:14:30 +00:00
format1.c	Introduce memory pool per volume group.	2009-04-10 09:59:18 +00:00
format1.h	split orphan VG by format type	2008-02-06 15:47:28 +00:00
import-export.c	Right, a simple build (without options) is working again.	2008-11-03 22:14:30 +00:00
import-extents.c	Right, a simple build (without options) is working again.	2008-11-03 22:14:30 +00:00
layout.c	Some whitespace tidy-ups.	2008-01-30 14:00:02 +00:00
lvm1-label.c	Right, a simple build (without options) is working again.	2008-11-03 22:14:30 +00:00
lvm1-label.h	Fix inconsistent licence notices: executables are GPLv2; libraries LGPLv2.1.	2007-08-20 20:55:30 +00:00
Makefile.in	Right, a simple build (without options) is working again.	2008-11-03 22:14:30 +00:00
vg_number.c	Right, a simple build (without options) is working again.	2008-11-03 22:14:30 +00:00