From: Zdenek Kabelac <zkabelac@redhat.com>
To: lvm-devel@redhat.com
Subject: [PATCH] Pass parsed metadata to activation code.
Date: Wed, 20 Mar 2013 10:07:54 +0100 [thread overview]
Message-ID: <51497C6A.80500@redhat.com> (raw)
In-Reply-To: <8738vrc634.fsf@mornfall.net> (sfid-20130320_003928_215503_2A328EE0)
Dne 20.3.2013 00:39, Petr Rockai napsal(a):
> Hi,
>
> the actual patches can be seen as follows:
>
> $ git clone http://repos.mornfall.net/lvm2/mornfall.git
> $ git checkout origin/mornfall
> $ git log 6a995ba..65718c8 -p
>
I've went into very quick overview - would it be possible to split some
patches into 'rename/clean old code' 'add new functionality' ?
Also - how does the new solution 'scales' in terms of having thousands of LVs
in the metadata - I've noticed couple new linear scans 'dm_list_iterate()'.
The trick with lv_ondisk() code is not yet very clean to me - will need to
find some time for this - it seems to be adding new complexity in the code.
Zdenek
next prev parent reply other threads:[~2013-03-20 9:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-19 23:39 [PATCH] Pass parsed metadata to activation code Petr Rockai
2013-03-20 9:07 ` Zdenek Kabelac [this message]
2013-03-20 11:11 ` [Red Hat - Possible Forgery] " Petr Rockai
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=51497C6A.80500@redhat.com \
--to=zkabelac@redhat.com \
--cc=lvm-devel@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.