From: Dan Mick <dan.mick@inktank.com>
To: Stefan Priebe <s.priebe@profihost.ag>
Cc: "ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>
Subject: Re: rbd STDIN import does not work / wip-rbd-export-stdout
Date: Sat, 01 Dec 2012 16:28:14 -0800 [thread overview]
Message-ID: <50BAA09E.9070506@inktank.com> (raw)
In-Reply-To: <50BA6746.4010609@profihost.ag>
On 12/1/2012 12:23 PM, Stefan Priebe wrote:
> Hi Dan,
>
> Am 27.11.2012 10:16, schrieb Stefan Priebe - Profihost AG:
>> Am 26.11.2012 21:00, schrieb Dan Mick:
>>> It writes zeros; there's no way for it to know how many zeros are
>>> coming. It could make a half-hearted attempt depending on its buffer
>>> size and the amount of data the source is willing to buffer.
>
> Yes but why not skip at leas if the WHOLE BUFFER is zero and then use
> the buffer size = stripe size?
>
> Right now a 40GB image which has just 3GB used rest is zeros due to
> using fstrim before doing the export takes a long time to import. We
> could speed this up a lot if we would skip parts with only zeros.
Great minds! I'm actually working on that now; as you say it's not hard.
> Greets,
> Stefab
prev parent reply other threads:[~2012-12-02 0:28 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-26 13:20 rbd STDIN import does not work / wip-rbd-export-stdout Stefan Priebe - Profihost AG
2012-11-26 13:29 ` Oliver Francke
2012-11-26 13:35 ` Stefan Priebe - Profihost AG
2012-11-26 17:34 ` Dan Mick
2012-11-26 19:35 ` Stefan Priebe - Profihost AG
2012-11-26 20:00 ` Dan Mick
2012-11-27 9:16 ` Stefan Priebe - Profihost AG
2012-11-27 22:50 ` Josh Durgin
2012-11-28 8:09 ` Stefan Priebe - Profihost AG
2012-11-28 18:51 ` Josh Durgin
2012-11-29 10:26 ` Stefan Priebe - Profihost AG
2012-11-28 14:53 ` Stefan Priebe - Profihost AG
2012-12-02 0:27 ` Dan Mick
2012-12-01 20:23 ` Stefan Priebe
2012-12-02 0:28 ` Dan Mick [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=50BAA09E.9070506@inktank.com \
--to=dan.mick@inktank.com \
--cc=ceph-devel@vger.kernel.org \
--cc=s.priebe@profihost.ag \
/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.