From: Alasdair G Kergon <agk@redhat.com>
To: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] vgchange -a memory consumption
Date: Sat, 12 Jul 2008 17:51:45 +0100 [thread overview]
Message-ID: <20080712165145.GC7155@agk.fab.redhat.com> (raw)
In-Reply-To: <1215842251.3751.53.camel@desktop>
On Fri, Jul 11, 2008 at 10:57:31PM -0700, Daniel Stodden wrote:
> I'm running, lvm2-2.02.26.
Don't bother investigating that version - stuff got changed.
Update to the latest release (or CVS) and try again.
> Why is that data reread?
Because the two parts of the code are designed to be independent. - The
so-called "activation" code sits behind an API in a so-called "locking"
module. There's a choice of locking modules, and some send the requests
around a cluster of machines - remote machines will only run the
activation code and manage the metadata independently. We just pass
UUIDs through the cluster communication layer, never metadata itself.
> Second: why isn't that memory freed after returning from
> activate_lv?
It's released after processing the whole command. If there are cases
where too much is still being held while processing in the *current*
version of the code, then yes, you might be able to free parts of it
sooner.
Alasdair
--
agk@redhat.com
next prev parent reply other threads:[~2008-07-12 16:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-12 5:57 [linux-lvm] vgchange -a memory consumption Daniel Stodden
2008-07-12 16:51 ` Alasdair G Kergon [this message]
2008-07-15 6:19 ` Daniel Stodden
2008-07-16 16:48 ` [PATCH] " Daniel Stodden
[not found] ` <20080716165243.GM7155@agk.fab.redhat.com>
[not found] ` <1216228176.1130.13.camel@desktop>
[not found] ` <20080716174240.GN7155@agk.fab.redhat.com>
[not found] ` <1216231344.16876.25.camel@desktop>
2008-07-16 18:08 ` Daniel Stodden
2008-07-16 20:39 ` [PATCH2] " Daniel Stodden
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20080712165145.GC7155@agk.fab.redhat.com \
--to=agk@redhat.com \
--cc=linux-lvm@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.