From: Loic Dachary <loic@dachary.org>
To: Li Wang <liwang@ubuntukylin.com>
Cc: "ceph-devel@vger.kernel.org" <ceph-devel@vger.kernel.org>
Subject: Re: Blueprint: inline data support (step 2)
Date: Wed, 31 Jul 2013 02:17:57 +0200 [thread overview]
Message-ID: <51F857B5.5070409@dachary.org> (raw)
In-Reply-To: <51F855D9.6070306@ubuntukylin.com>
[-- Attachment #1: Type: text/plain, Size: 1021 bytes --]
Hi,
It would be nice to have URLs to the current implementation and the benchmark results you got in the blueprint.
http://wiki.ceph.com/01Planning/02Blueprints/Emperor/Inline_data_support_%28Step_2%29
Cheers
On 31/07/2013 02:10, Li Wang wrote:
> We have worked out a preliminary implementation for inline data support, and observed obvious speed up for small file access.
>
> The step 2 will focus on (1) Try to make things simpler to eliminate the state of a file half-inlined; (2) To efficiently deal with the share write or read/write; (3) Protocal backword compatability
>
> We submitted a blueprint for this, anyone interested is welcome to join the discussion.
> --
> To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
--
Loïc Dachary, Artisan Logiciel Libre
All that is necessary for the triumph of evil is that good people do nothing.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 261 bytes --]
next prev parent reply other threads:[~2013-07-31 0:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-31 0:10 Blueprint: inline data support (step 2) Li Wang
2013-07-31 0:17 ` Loic Dachary [this message]
2013-07-31 14:34 ` Li Wang
2013-08-09 18:18 ` Sage Weil
2013-08-11 4:29 ` Li Wang
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=51F857B5.5070409@dachary.org \
--to=loic@dachary.org \
--cc=ceph-devel@vger.kernel.org \
--cc=liwang@ubuntukylin.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