From: Jun'ichi Nomura <j-nomura@ce.jp.nec.com>
To: lvm-devel@redhat.com
Subject: [LVM2 PATCH] (1/5) Separate mirror log allocation from _alloc_parallel_areas()
Date: Mon, 08 Jan 2007 12:11:24 -0500 [thread overview]
Message-ID: <45A27B3C.7070301@ce.jp.nec.com> (raw)
In-Reply-To: <45A2751E.5010707@ce.jp.nec.com>
This patch moves the log allocation part from _alloc_parallel_area().
Preparation for the following patches.
No functional change.
- _alloc_parallel_area() doesn't need to allocate struct alloced_area
for log_area because it's pre-allocated in struct alloc_handle.
- consume_pv_area() has been done in the separate loop from
the loop for struct alloced_area setup.
However, consume_pv_area() just updates given pv_area and
pv_areas in areas[] are different each other.
So it can be done in the same loop with the struct alloced_area setup.
- ah->total_area_len, area_len, *ix and ah->area_multiple are not
used/updated in log_area allocation.
So operation on them can be moved before _alloc_log_area().
Thanks,
--
Jun'ichi Nomura, NEC Corporation of America
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 01-separate-mirror-log-allocation-from-alloc_parallel_area.patch
Type: text/x-patch
Size: 2553 bytes
Desc: not available
URL: <http://listman.redhat.com/archives/lvm-devel/attachments/20070108/2d91c213/attachment.bin>
next parent reply other threads:[~2007-01-08 17:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <45A2751E.5010707@ce.jp.nec.com>
2007-01-08 17:11 ` Jun'ichi Nomura [this message]
2007-01-08 17:11 ` [LVM2 PATCH] (2/5) Fix mirror-log-only allocation failure Jun'ichi Nomura
2007-01-08 17:11 ` [LVM2 PATCH] (3/5) Allocate mirror log first Jun'ichi Nomura
2007-01-08 17:11 ` [LVM2 PATCH] (4/5) Remove unnecessary prev_lvseg checks Jun'ichi Nomura
2007-01-08 17:12 ` [LVM2 PATCH] (5/5) Remove ix_offset 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=45A27B3C.7070301@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.