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 6/6] Remove unused can_split param from allocate_extents()
Date: Thu, 06 Dec 2007 11:51:49 -0500	[thread overview]
Message-ID: <475828A5.3070400@ce.jp.nec.com> (raw)
In-Reply-To: <475825EF.6000803@ce.jp.nec.com>

'can_split' was a parameter to specify that the allocation should
not be splitted even if the policy is not ALLOC_CONTIGUOUS.
It was there for pvmove, which was not able to handle splitted
allocation.

However, since pvmove now can handle splitted destinations,
we can remove the param from allocate_extents().

Thanks,
-- 
Jun'ichi Nomura, NEC Corporation of America
-------------- next part --------------
A non-text attachment was scrubbed...
Name: lvm2-remove-unused-can_split-args.patch
Type: text/x-patch
Size: 3628 bytes
Desc: not available
URL: <http://listman.redhat.com/archives/lvm-devel/attachments/20071206/17554318/attachment.bin>

  parent reply	other threads:[~2007-12-06 16:51 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-06 16:40 [PATCH pvmove 0/6] Refactoring pvmove with generic APIs Jun'ichi Nomura
2007-12-06 16:48 ` [PATCH pvmove 1/6] Add insert_layer_for_segments_on_pv() Jun'ichi Nomura
2007-12-06 16:48 ` [PATCH pvmove 2/6] Add convert_segments_mirrored() Jun'ichi Nomura
2007-12-06 16:49 ` [PATCH pvmove 3/6] Add split_parent_segments() Jun'ichi Nomura
2007-12-06 16:50 ` [PATCH pvmove 4/6] Change pvmove to use the generalized APIs Jun'ichi Nomura
2007-12-06 16:51 ` [PATCH pvmove 5/6] Remove unused mirrored_pv/mirrored_pe params from internal code Jun'ichi Nomura
2007-12-06 16:51 ` Jun'ichi Nomura [this message]
2007-12-06 16:53 ` [PATCH pvmove 0/6] Refactoring pvmove with generic APIs Jun'ichi Nomura
2007-12-07 11:49 ` Heinz Mauelshagen
2007-12-07 15:48   ` 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=475828A5.3070400@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.