From: Mike Snitzer <snitzer@redhat.com>
To: lilofile <lilofile@aliyun.com>
Cc: Ondrej Kozina <okozina@redhat.com>,
device-mapper development <dm-devel@redhat.com>,
"Alasdair G. Kergon" <agk@redhat.com>
Subject: Re: Thinly-Provisioned Logical Volumes
Date: Mon, 22 Sep 2014 08:38:38 -0400 [thread overview]
Message-ID: <20140922123837.GA5191@redhat.com> (raw)
In-Reply-To: <b3abf2cc-2219-4b5a-b546-5f71301c40e4@aliyun.com>
On Sat, Sep 20 2014 at 10:19am -0400,
lilofile <lilofile@aliyun.com> wrote:
> when I test Thinly-Provisioned Logical Volumes(use device thinprovison
> target),I found the random write performance is very low. What factors
> will influence the random write performance of thin volume.
It is worth reading this blog post from Joe:
http://device-mapper.org/blog/2014/01/21/random-io-and-copy-on-write-schemes/
> how can i quickly understand dm-bufio.c?
What is it you'd like to know? dm-bufio.c isn't the smoking gun for
random write performance being slow though. It is more to do with the
natural impact random writes have on thinp (as discussed in the above
article).
next prev parent reply other threads:[~2014-09-22 12:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-20 14:19 Thinly-Provisioned Logical Volumes lilofile
2014-09-22 7:02 ` Zdenek Kabelac
2014-09-22 12:38 ` Mike Snitzer [this message]
2014-09-23 13:51 ` reply： " lilofile
2014-09-23 14:07 ` Zdenek Kabelac
2014-09-24 2:11 ` lilofile
2014-09-24 7:02 ` Zdenek Kabelac
2014-09-24 8:37 ` Joe Thornber
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=20140922123837.GA5191@redhat.com \
--to=snitzer@redhat.com \
--cc=agk@redhat.com \
--cc=dm-devel@redhat.com \
--cc=lilofile@aliyun.com \
--cc=okozina@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.