All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jun'ichi Nomura <j-nomura@ce.jp.nec.com>
To: lvm-devel@redhat.com
Subject: [PATCH pvmove 3/9] Add split_parent_segments_for_layer()
Date: Thu, 13 Dec 2007 16:03:37 -0500	[thread overview]
Message-ID: <47619E29.2050407@ce.jp.nec.com> (raw)
In-Reply-To: <476198D3.1080003@ce.jp.nec.com>

Add split_parent_segments_for_layer().

The function walks through LVs in the VG.
For each lv segment, check if it's on multiple layer segments.
If so, split the lv segment so that only 1 layer segment is under
the lv segment.

For example, a segment on pvmove layer is a source segment of the move.
If there are multiple underlying pvmove segments, it means the
destination is splitted and the source segment should be splitted
when the move completes.
The function is a helper for cases like this.

Changes since rev2:
  * Changed function names to more specific ones
      - split_parent_segments() -> split_parent_segments_for_layer()
      - _split_parent_segment() -> _split_parent_area()
  * Added cmd_context argument to split_parent_segments_for_layer.
  * Use build_parallel_areas() to find the lowest-level segment boundaries
    for layer LV.
  * Introduced _find_seg_pvs_by_le().
  * Add incompatible boundary check in _split_parent_area()
    (e.g. the layer segments are mistakenly merged.)

Thanks,
-- 
Jun'ichi Nomura, NEC Corporation of America
-------------- next part --------------
A non-text attachment was scrubbed...
Name: lvm2-split-parent-segments.patch
Type: text/x-patch
Size: 4427 bytes
Desc: not available
URL: <http://listman.redhat.com/archives/lvm-devel/attachments/20071213/a88849a6/attachment.bin>

  parent reply	other threads:[~2007-12-13 21:03 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-13 20:40 [PATCH pvmove 0/9] Refactoring pvmove with generic APIs (rev. 3) Jun'ichi Nomura
2007-12-13 21:03 ` [PATCH pvmove 1/9] Add insert_layer_for_segments_on_pv() Jun'ichi Nomura
2007-12-13 21:03 ` [PATCH pvmove 2/9] Add add_mirrors_to_segments() Jun'ichi Nomura
2007-12-13 21:03 ` Jun'ichi Nomura [this message]
2007-12-13 21:03 ` [PATCH pvmove 4/9] Change pvmove to use the generalized APIs Jun'ichi Nomura
2007-12-13 21:03 ` [PATCH pvmove 5/9] Remove unused mirrored_pv/mirrored_pe params from internal code Jun'ichi Nomura
2007-12-13 21:03 ` [PATCH pvmove 6/9] Remove unused can_split param from allocate_extents() Jun'ichi Nomura
2007-12-13 21:03 ` [PATCH pvmove 7/9] Add remove_mirrors_from_segments() and remove_layer_from_segments() Jun'ichi Nomura
2007-12-13 21:04 ` [PATCH pvmove 8/9] Change pvmove to use the generalized mirror-removal APIs Jun'ichi Nomura
2007-12-13 21:04 ` [PATCH pvmove 9/9] Remove unused remove_pvmove_mirrors() Jun'ichi Nomura
2007-12-13 21:04 ` [PATCH pvmove Appendix] pvmove test cases for 'make check' 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=47619E29.2050407@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.