Milan Broz 06bdf8b461 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

Missing .exported_symbols

2004-06-24 08:16:09 +00:00

cluster_locking.c

Rename 'cmd' to 'clvmd_cmd' to remove ambiguity.

2008-12-16 12:30:39 +00:00

external_locking.c

Some whitespace tidy-ups.

2008-01-30 14:00:02 +00:00

file_locking.c

* minor compilator warning fix for improper function declaration.

2008-11-12 09:30:52 +00:00

locking_types.h

Clean up numerous compiler warnings that crept in recently.

2007-08-22 14:38:18 +00:00

locking.c

Fix interrupt unblocking after vgcreate, for example: drop_cached_metadata()

2009-02-22 16:13:57 +00:00

locking.h

Introduce memory pool per volume group.

2009-04-10 09:59:18 +00:00

Makefile.in

Right, a simple build (without options) is working again.

2008-11-03 22:14:30 +00:00

no_locking.c

Update lvmcache VG lock state for all locking types now.

2008-04-07 19:17:29 +00:00