All of lore.kernel.org
 help / color / mirror / Atom feed
From: Zdenek Kabelac <zkabelac@redhat.com>
To: lvm-devel@redhat.com
Subject: [PATCH 0/4] Alloc VG
Date: Wed,  2 Mar 2011 19:20:22 +0100	[thread overview]
Message-ID: <cover.1299089601.git.zkabelac@redhat.com> (raw)

Refactor allocation of volume group structure.

Patch is currently splitted into multiple files to make a review easier.

Things to check - why is pool_vg_read used  seqno == 1?
(To make it same for all - I'd leave to 0 ?)

Memory for import functions is always used from vg mempool.

Future updates -
It would be probably worth to switch vg name to  char[128] (max vg name len)
to simplify surrounding allocations...


Zdenek Kabelac (4):
  Refactor vg allocation code
  Use alloc_vg for _pool_vg_read
  Use allog_vg for _free_vg in _pvsegs_sub_single
  Use alloc_vg for forma1_vg_read

 lib/format1/format1.c         |   72 ++++++++++---------------------
 lib/format_pool/format_pool.c |   96 ++++++++++++++---------------------------
 lib/format_text/import_vsn1.c |   38 +++++-----------
 lib/metadata/metadata.c       |   75 ++++++-------------------------
 lib/metadata/vg.c             |   32 ++++++++++++++
 lib/metadata/vg.h             |    3 +
 tools/reporter.c              |   25 +++++------
 7 files changed, 128 insertions(+), 213 deletions(-)

-- 
1.7.4.1



             reply	other threads:[~2011-03-02 18:20 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-02 18:20 Zdenek Kabelac [this message]
2011-03-02 18:20 ` [PATCH 1/4] Refactor vg allocation code Zdenek Kabelac
2011-03-02 18:20 ` [PATCH 2/4] Use alloc_vg for _pool_vg_read Zdenek Kabelac
2011-03-02 18:20 ` [PATCH 3/4] Use allog_vg for _free_vg in _pvsegs_sub_single Zdenek Kabelac
2011-03-08 17:09   ` Alasdair G Kergon
2011-03-08 22:30     ` Zdenek Kabelac
2011-03-09  3:01       ` Alasdair G Kergon
2011-03-09  8:51         ` Zdenek Kabelac
2011-03-02 18:20 ` [PATCH 4/4] Use alloc_vg for forma1_vg_read Zdenek Kabelac

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=cover.1299089601.git.zkabelac@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.