From: Mike Snitzer <snitzer@redhat.com>
To: Linda Walsh <lvm@tlinx.org>
Cc: LVM general discussion and development <linux-lvm@redhat.com>
Subject: Re: [linux-lvm] RFE? Really power of 2? extents, chunks and raid alignment
Date: Wed, 25 Jul 2012 17:04:34 -0400 [thread overview]
Message-ID: <20120725210434.GA20135@redhat.com> (raw)
In-Reply-To: <500C44EF.4080004@tlinx.org>
On Sun, Jul 22 2012 at 2:22pm -0400,
Linda Walsh <lvm@tlinx.org> wrote:
>
>
>
> I was trying to figure out why I didn't get performance out of my RAID,
> except when operating on really large files where it's many stripes
> v. 1 stripe.
>
> I have 12 data disks in a RAID 50 (3 RAID5's in a RAID0) and use a suggested
> stripesize of 64k, so a stripe-width of 768k.
>
> Some issues that have been nagging me though are getting my allocations
> lined up on 768k boundaries. xfs is no prob -- tell it 64k and 12
> and it does it.
>
> But I just realized that lvm doesn't really tell me where it is
> aligning things
> and worse, only lets me align both chunksizes for lv's and extents for vg's
> in powers of 2. Um... Not a multiple of 4k? or 64k?
>
> Am I wrong in thinking this would tend to give me both pv's and lv's that
> are very likely NOT to be stripe-width aligned, but, worse, not stripewidth
> alignable, at all.
>
> This would mean that a high performance file system aware of RAID
> stripe with
> that tries to allocate chunks starting on a 768k boundary are likely
> to just
> get it completely wrong? No?
>
> Or what am I missing?
The DM update for the 3.6 merge window adds non power of 2 support in
the kernel (for the stripe and thin-pool targets).
So the lvm2 constraints that require a power of 2 chunksize will be
relaxed very shortly.
next prev parent reply other threads:[~2012-07-25 21:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-22 18:22 [linux-lvm] RFE? Really power of 2? extents, chunks and raid alignment Linda Walsh
2012-07-25 20:06 ` Lars Ellenberg
2012-08-01 23:32 ` Linda A. Walsh
2012-07-25 21:04 ` Mike Snitzer [this message]
2012-07-25 22:34 ` Linda Walsh
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=20120725210434.GA20135@redhat.com \
--to=snitzer@redhat.com \
--cc=linux-lvm@redhat.com \
--cc=lvm@tlinx.org \
/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.