linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Doug Ledford <dledford@redhat.com>
To: "Darius S. Naqvi" <dnaqvi@datagardens.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: bitmap chunk size
Date: Tue, 10 Nov 2009 13:01:54 -0500	[thread overview]
Message-ID: <4AF9AA92.7030604@redhat.com> (raw)
In-Reply-To: <alpine.DEB.1.00.0911100933160.10087@darius>

[-- Attachment #1: Type: text/plain, Size: 1289 bytes --]

On 11/10/2009 11:39 AM, Darius S. Naqvi wrote:
> Is there any possibility of having a bitmap chunk size of 512 bytes?
> I know that mdadm rejects anything under 4k.  I fear that the
> assumption of the 4k minimum is embedded fairly strongly in the code.
> Can my fear be alleviated?
> 

If you're putting any normal filesystem (with a block size of 4k) on
this, then it makes absolutely no sense to have a bitmap size less than
4k as any given filesystem block is either dirty or clean, sub-block
semantics make no sense in this scenario.  That said, unless you have a
specific need for this level of granularity, it is a really bad idea
(performance wise and space wise) to go with anything even close to
resembling the granularity you are requesting.  I usually go with
--bitmap-chunk=32768 (which since that's expressed in k means
32Megabytes).  I would actually suspect that if you have a truly
pressing need for a 512byte bitmap chunk, then you probably don't need a
bare raid, you need some sort of database underlying your data or
something else.

-- 
Doug Ledford <dledford@redhat.com>
              GPG KeyID: CFBFF194
	      http://people.redhat.com/dledford

Infiniband specific RPMs available at
	      http://people.redhat.com/dledford/Infiniband


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

  reply	other threads:[~2009-11-10 18:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-10 16:39 bitmap chunk size Darius S. Naqvi
2009-11-10 18:01 ` Doug Ledford [this message]
2009-11-10 18:36   ` Darius S. Naqvi
2009-11-10 19:46     ` Doug Ledford

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=4AF9AA92.7030604@redhat.com \
    --to=dledford@redhat.com \
    --cc=dnaqvi@datagardens.com \
    --cc=linux-raid@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).