diff options
author | Peter Rajnoha <prajnoha@redhat.com> | 2011-08-29 13:37:36 +0000 |
---|---|---|
committer | Peter Rajnoha <prajnoha@redhat.com> | 2011-08-29 13:37:36 +0000 |
commit | d35188058be01bd29128dcf1f5b79220fbcb135b (patch) | |
tree | 3266486483756631c78900afb86efa12c1e18556 /lib/raid/raid.c | |
parent | 11bfaa1df8a1cae26a891c128f9bbaf8116c9453 (diff) | |
download | lvm2-d35188058be01bd29128dcf1f5b79220fbcb135b.tar.gz lvm2-d35188058be01bd29128dcf1f5b79220fbcb135b.tar.xz lvm2-d35188058be01bd29128dcf1f5b79220fbcb135b.zip |
Directly allocate buffer memory in a pvck scan instead of using a mempool.
There's a very high memory usage when calling _pv_analyse_mda_raw (e.g. while
executing pvck) that can end up with "out of memory".
_pv_analyse_mda_raw scans for metadata in the MDA, iteratively increasing the
size to scan with SECTOR_SIZE until we find a probable config section or we're
at the edge of the metadata area. However, when using a memory pool, we're also
iteratively chasing for bigger and bigger mempool chunk which can't be found
and so we're always allocating a new one, consuming more and more memory...
This patch just changes the mempool to direct memory allocation in this
problematic part of the code.
Diffstat (limited to 'lib/raid/raid.c')
0 files changed, 0 insertions, 0 deletions