From: Joe Thornber <thornber@redhat.com>
To: lvm-devel@redhat.com
Subject: [PATCH 1/6] Pool locking code
Date: Wed, 23 Mar 2011 07:53:47 -0700 [thread overview]
Message-ID: <1300892027.14527.29.camel@ubuntu> (raw)
In-Reply-To: <4D8A06F8.3070807@redhat.com>
On Wed, 2011-03-23 at 15:43 +0100, Zdenek Kabelac wrote:
> It's been my first idea - to copy all chunks to separate buffer - but the VG
> mempool size for large VGs is actually quite big - thus doing always a
> snapshot isn't performance optimal. I'm doing my tests with ~7000LV - and it
> would be quite noticable to copy all the pool chunks with each use of it.
Can you define 'quite big' please?
- Joe
next prev parent reply other threads:[~2011-03-23 14:53 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-22 21:21 [PATCH 0/6] VG share v2 Zdenek Kabelac
2011-03-22 21:21 ` [PATCH 1/6] Pool locking code Zdenek Kabelac
2011-03-23 14:03 ` Joe Thornber
2011-03-23 14:43 ` Zdenek Kabelac
2011-03-23 14:53 ` Joe Thornber [this message]
2011-03-23 14:54 ` Zdenek Kabelac
2011-03-23 15:13 ` Joe Thornber
2011-03-23 15:57 ` Zdenek Kabelac
2011-03-23 16:33 ` Zdenek Kabelac
2011-03-23 17:29 ` Zdenek Kabelac
2011-03-23 18:41 ` Joe Thornber
2011-03-23 19:01 ` Zdenek Kabelac
2011-03-24 12:21 ` Joe Thornber
2011-03-24 12:45 ` Zdenek Kabelac
2011-03-24 13:50 ` Zdenek Kabelac
2011-03-22 21:21 ` [PATCH 2/6] Code move vg_mark_partial up in stack Zdenek Kabelac
2011-03-22 21:21 ` [PATCH 3/6] Share VG multiple times Zdenek Kabelac
2011-03-22 21:21 ` [PATCH 4/6] Use dm_pool_set_uint64 Zdenek Kabelac
2011-03-22 21:21 ` [PATCH 5/6] lv_postorder using dm_pool_set_uint64 Zdenek Kabelac
2011-03-22 21:22 ` [PATCH 6/6] lv_postorder unlock and lock 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=1300892027.14527.29.camel@ubuntu \
--to=thornber@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.