From: Milan Broz <mbroz@redhat.com>
To: lvm-devel@redhat.com
Subject: [RFC PATCH v2] change default alignment of pe_start to 1MB
Date: Mon, 09 Aug 2010 18:28:17 +0200 [thread overview]
Message-ID: <4C602CA1.3040406@redhat.com> (raw)
In-Reply-To: <20100806041138.GA29995@redhat.com>
On 08/06/2010 06:11 AM, Mike Snitzer wrote:
> The switch to a 1MB default alignment causes various tests in the LVM2
> testsuite to fail -- not a big deal but the tests would need updating.
>
> Of more concern is that the existing LVM2 set_pe_align() code doesn't
> always properly respect the alignment determined from
> 'devices/md_chunk_alignment' or 'devices/data_alignment_detection'.
>
> With the previous default alignment of 64k it would generally do the
> right thing -- use the detected values. But switching the default to
> the larger value exposes the fact that MAX() of the MD or I/O Topology
> detected values will generally always be 1MB -- when they are compared
> to 1MB.
>
> The following revised patch changes the LVM alignment detection
> semantics to model what fdisk has elected to do:
> - If the default value (1MB) is a multiple of the specified/detected
> alignment then just use the default.
> - Otherwise, use the specified/detected value.
>
> In practice this means we'll almost always use 1MB -- that is unless:
> - the specified --dataalignment, MD's full stripe width, or the
> optimal_io_size exceeds 1MB
> - the specified/detected value is not a power-of-2
patch not tested, but Ack for idea.
(I just did independently the same for LUKS devices.)
Milan
next prev parent reply other threads:[~2010-08-09 16:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-05 19:10 [RFC PATCH] change default alignment of pe_start to 1MB Mike Snitzer
2010-08-06 4:11 ` [RFC PATCH v2] " Mike Snitzer
2010-08-09 16:28 ` Milan Broz [this message]
2010-08-09 16:42 ` Mike Snitzer
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=4C602CA1.3040406@redhat.com \
--to=mbroz@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.