dm-devel.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Zdenek Kabelac <zkabelac@redhat.com>
To: lilofile <lilofile@aliyun.com>,
	device-mapper development <dm-devel@redhat.com>,
	Mike Snitzer <snitzer@redhat.com>
Cc: Ondrej Kozina <okozina@redhat.com>, axboe <axboe@kernel.dk>,
	Edward Thornber <thornber@redhat.com>
Subject: Re: dm-thin
Date: Tue, 21 Oct 2014 11:32:54 +0200	[thread overview]
Message-ID: <54462846.7040502@redhat.com> (raw)
In-Reply-To: <20b42a29-27ce-4395-9cd9-843f2acfcab2@aliyun.com>

Dne 21.10.2014 v 03:36 lilofile napsal(a):
> In dm-thin.c,
> /*
>   * The block size of the device holding pool data must be
>   * between 64KB and 1GB.
>   */
> #define DATA_DEV_BLOCK_SIZE_MIN_SECTORS (64 * 1024 >> SECTOR_SHIFT)
> #define DATA_DEV_BLOCK_SIZE_MAX_SECTORS (1024 * 1024 * 1024 >> SECTOR_SHIFT)
>
> why the block size must be between 64KB and 1GB, can I change  the value of DATA_DEV_BLOCK_SIZE_MIN_SECTORS? what effect  if the value of DATA_DEV_BLOCK_SIZE_MIN_SECTORS<128?


Performance reasons mainly - updating metadata much more frequently is 
lowering the throughput considerable.

The other issue is you would also scale up required metadata size.

Zdenek

      reply	other threads:[~2014-10-21  9:32 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-13 15:27 A patchset to limit the number of outstanding bios Mikulas Patocka
2014-10-13 16:03 ` Joe Thornber
2014-10-13 16:20 ` Mike Snitzer
2014-10-13 20:52   ` Mikulas Patocka
2014-10-15 12:12   ` device-mapper lilofile
2014-10-21  1:36   ` dm-thin lilofile
2014-10-21  9:32     ` Zdenek Kabelac [this message]

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=54462846.7040502@redhat.com \
    --to=zkabelac@redhat.com \
    --cc=axboe@kernel.dk \
    --cc=dm-devel@redhat.com \
    --cc=lilofile@aliyun.com \
    --cc=okozina@redhat.com \
    --cc=snitzer@redhat.com \
    --cc=thornber@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 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).