From: Joe Thornber <thornber@redhat.com>
To: device-mapper development <dm-devel@redhat.com>
Cc: "Alasdair G. Kergon" <agk@redhat.com>
Subject: Re: [PATCH] dm-kcopyd/dm-snap: Don't read the origin on full chunk write
Date: Mon, 20 Jun 2011 09:09:53 +0100 [thread overview]
Message-ID: <20110620080952.GA3266@ubuntu> (raw)
In-Reply-To: <Pine.LNX.4.64.1106170829390.24411@hs20-bc2-1.build.redhat.com>
On Fri, Jun 17, 2011 at 08:32:36AM -0400, Mikulas Patocka wrote:
> Hi
>
> This optimizes full chunk writes for snapshots.
>
> Note that there is a performance bug in device mapper that it doesn't ever
> send bios larger than 4k to snapshots. So this patch optimizes only 4k
> chunk sizes. Once the 4k limit will be removed from device mapper, this
> patch could optimize any chunk size.
Nack. If you don't need to copy, don't send it to kcopyd.
- Joe
next prev parent reply other threads:[~2011-06-20 8:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-17 12:32 [PATCH] dm-kcopyd/dm-snap: Don't read the origin on full chunk write Mikulas Patocka
2011-06-20 8:09 ` Joe Thornber [this message]
2011-06-20 9:51 ` Milan Broz
2011-06-20 10:03 ` Joe Thornber
-- strict thread matches above, loose matches on Subject: below --
2011-06-24 0:25 Mikulas Patocka
2011-06-24 0:51 ` Alasdair G Kergon
2011-06-24 7:35 ` 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=20110620080952.GA3266@ubuntu \
--to=thornber@redhat.com \
--cc=agk@redhat.com \
--cc=dm-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.