From: Alasdair G Kergon <agk@redhat.com>
To: device-mapper development <dm-devel@redhat.com>
Subject: Re: [RFC] [PATCH] lvm2: mirroredlog support
Date: Wed, 30 Sep 2009 17:35:20 +0100 [thread overview]
Message-ID: <20090930163519.GV5351@agk-dp.fab.redhat.com> (raw)
In-Reply-To: <F5472B5D-59E5-4A38-948B-6055886E75A8@redhat.com>
On Wed, Sep 30, 2009 at 10:50:06AM -0500, Jon Brassow wrote:
> As long as we are on the topic of mirror logs (and this is unrelated to
> your patch), I'd like to complain about the current behavior of log
> allocation vs the log policy. I don't think it should take
> 'alloc_anywhere' for a log to be placed on the same disk as one of the
> mirror legs... that should be 'alloc_normal'.
It was assumed that performance would be better this way, but I have
never seen any tests to prove or disprove that. Maybe someone could run
some?
One way we could handle this is by creating a new policy between
NORMAL and ANYWHERE that does this, then renaming the old NORMAL
to something else and the new policy to NORMAL.
Alasdair
next prev parent reply other threads:[~2009-09-30 16:35 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-23 3:03 [RFC] [PATCH] lvm2: mirroredlog support malahal
2009-09-23 20:29 ` Jonathan Brassow
2009-09-23 20:44 ` malahal
2009-09-24 5:22 ` Takahiro Yasui
2009-09-30 15:50 ` Jonathan Brassow
2009-09-30 16:35 ` Alasdair G Kergon [this message]
2009-09-30 19:48 ` Jonathan Brassow
2009-09-30 21:18 ` Alasdair G Kergon
2009-09-30 21:46 ` Alasdair G Kergon
2009-09-30 21:19 ` malahal
2009-10-01 0:13 ` malahal
-- strict thread matches above, loose matches on Subject: below --
2008-12-30 0:10 malahal
2008-12-30 0:10 ` malahal
2009-01-19 22:56 ` Takahiro Yasui
2009-01-20 1:54 ` malahal
2009-01-20 22:12 ` Takahiro Yasui
2009-01-20 21:29 ` Takahiro Yasui
2009-01-20 22:14 ` malahal
2009-01-23 19:14 ` Jonathan Brassow
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=20090930163519.GV5351@agk-dp.fab.redhat.com \
--to=agk@redhat.com \
--cc=dm-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.