From: Jun'ichi Nomura <j-nomura@ce.jp.nec.com>
To: lvm-devel@redhat.com
Subject: [PATCH lvconvert 4/6] Change lvcreate to use the new mirror APIs
Date: Thu, 13 Dec 2007 16:31:35 -0500 [thread overview]
Message-ID: <4761A4B7.902@ce.jp.nec.com> (raw)
In-Reply-To: <47619E84.2060905@ce.jp.nec.com>
Change lvconvert to use add_mirror_images().
The patch simplifies the lvcreate code and we no longer need
to export allocate_extents() directly to tools.
However, this patch slightly changes the allocation logic.
Original code allocated all mirrors at once.
OTOH, this code creates a linear LV first then adds mirrors to it.
It's better to allocate all at once because otherwise the allocation
code may make worse choice at the first attempt.
To do that, we have to be able to create an empty mirror layers.
Thanks,
--
Jun'ichi Nomura, NEC Corporation of America
-------------- next part --------------
A non-text attachment was scrubbed...
Name: lvm2-lvcreate-use-new-mirror-api.patch
Type: text/x-patch
Size: 3257 bytes
Desc: not available
URL: <http://listman.redhat.com/archives/lvm-devel/attachments/20071213/174fcfbb/attachment.bin>
next prev parent reply other threads:[~2007-12-13 21:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-13 21:05 [PATCH lvconvert 0/6] Refactoring lvconvert mirror Jun'ichi Nomura
2007-12-13 21:31 ` [PATCH lvconvert 1/6] Add insert_layer_for_lv() / remove_layer_from_lv() Jun'ichi Nomura
2007-12-13 21:31 ` [PATCH lvconvert 2/6] Add add_mirror_images() / {add, remove}_mirror_log() Jun'ichi Nomura
2007-12-13 21:31 ` [PATCH lvconvert 3/6] Change lvconvert to use the new mirror APIs Jun'ichi Nomura
2007-12-13 21:31 ` Jun'ichi Nomura [this message]
2007-12-13 21:31 ` [PATCH lvconvert 5/6] Remove unused mirror functions Jun'ichi Nomura
2007-12-13 21:31 ` [PATCH lvconvert 6/6] Add lv_{add,remove}_mirrors() Jun'ichi Nomura
2007-12-13 21:32 ` [PATCH lvconvert Appendix] Experimental: pvmove with disk log and seg-by-seg mirrored LV Jun'ichi Nomura
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=4761A4B7.902@ce.jp.nec.com \
--to=j-nomura@ce.jp.nec.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.