From: Loic Dachary <loic@dachary.org>
To: "Miyamae, Takeshi" <miyamae.takeshi@jp.fujitsu.com>
Cc: Ceph Development <ceph-devel@vger.kernel.org>,
"Shiozawa, Kensuke" <shiozawa.kennsu@jp.fujitsu.com>,
"Nakao, Takanori" <nakao.takanori@jp.fujitsu.com>
Subject: Re: Deadline of Github pull request for Hammer release (question)
Date: Mon, 26 Jan 2015 12:02:45 +0100 [thread overview]
Message-ID: <54C61ED5.5040603@dachary.org> (raw)
In-Reply-To: <870DE8DBB716524BAE51B2D499EC81E40AA66142@g01jpexmbyt24>
[-- Attachment #1: Type: text/plain, Size: 3272 bytes --]
Hi,
Thanks for the snippet, I'll add it to the non regression from the pull request you sent :-)
Cheers
On 26/01/2015 06:43, Miyamae, Takeshi wrote:
> Hi Loic,
>
>> Note that you also need to update
>
> We have prepared mSHEC's parameter sets which we think will be commonly used.
> Because I'm not sure how to update another person's repository, we will write down
> those parameter sets in this mail.
> If we are required to do something, please let us know.
>
> while read k m c ; do
> for stripe_width in $STRIPE_WIDTHS ; do
> ceph_erasure_code_non_regression --stripe-width $stripe_width --plugin shec --parameter technique=multiple --parameter k=$k --parameter m=$m --parameter c=$c $ACTION $VERBOSE $MYDIR
> done
> done <<EOF
> 1 1 1
> 2 1 1
> 3 2 1
> 3 2 2
> 3 3 2
> 4 1 1
> 4 2 2
> 4 3 2
> 5 2 1
> 6 3 2
> 6 4 2
> 6 4 3
> 7 2 1
> 8 3 2
> 8 4 2
> 8 4 3
> 9 4 2
> 9 5 3
> 12 7 4
> EOF
>
> Best regards,
> Takeshi Miyamae
>
> -----Original Message-----
> From: Loic Dachary [mailto:loic@dachary.org]
> Sent: Friday, January 23, 2015 10:47 PM
> To: Miyamae, Takeshi/宮前 剛
> Cc: Ceph Development; Shiozawa, Kensuke/塩沢 賢輔; Nakao, Takanori/中尾 鷹詔
> Subject: Re: Deadline of Github pull request for Hammer release (question)
>
> Hi,
>
> Note that you also need to update
>
> https://github.com/dachary/ceph-erasure-code-corpus/blob/master/v0.85-764-gf3a1532/non-regression.sh
>
> to include non regression tests for the most common cases of the SHEC plugin encoding / decoding. This is run by make check (this repository is a submodule of Ceph). It helps make sure that content encoded / decoded with a given version of the plugin can be encoded / decoded exactly in the same way by all future versions.
>
> Cheers
>
> On 06/01/2015 12:49, Miyamae, Takeshi wrote:
>> Dear Loic,
>>
>> I'm Takeshi Miyamae, one of the authors of SHEC's blueprint.
>>
>> Shingled Erasure Code (SHEC)
>> https://wiki.ceph.com/Planning/Blueprints/Hammer/Shingled_Erasure_Code
>> _(SHEC)
>>
>> We have revised our blueprint shown in the last CDS to extend our
>> erasure code layouts and describe the guideline for choosing SHEC among various EC plugins.
>> We believe the blueprint now answers all the comments given at the CDS.
>>
>> In addition, we would like to ask for your advice on the schedule of
>> our github pull request. More specifically, we would like to know its
>> deadline for Hammer release.
>> (As we have not really completed our verification of SHEC, we are
>> wondering if we should make it open for early preview.)
>>
>> Thank you in advance,
>> Takeshi Miyamae
>>
>> --
>> 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
>
> N�����r��y���b�X��ǧv�^�){.n�+���z�]z���{ay�\x1dʇڙ�,j\a��f���h���z�\x1e�w���\f���j:+v���w�j�m����\a����zZ+�����ݢj"��!tml=
>
--
Loïc Dachary, Artisan Logiciel Libre
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2015-01-26 11:02 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-06 11:49 Deadline of Github pull request for Hammer release (question) Miyamae, Takeshi
2015-01-06 15:51 ` Loic Dachary
2015-01-13 10:24 ` Miyamae, Takeshi
2015-01-13 10:26 ` Loic Dachary
2015-01-13 10:34 ` Miyamae, Takeshi
2015-01-13 12:45 ` Loic Dachary
2015-01-13 17:05 ` Miyamae, Takeshi
2015-01-13 18:03 ` Loic Dachary
2015-01-20 0:48 ` Miyamae, Takeshi
2015-01-20 7:22 ` Loic Dachary
2015-01-20 9:07 ` Miyamae, Takeshi
2015-01-21 14:12 ` Loic Dachary
2015-01-22 8:42 ` Miyamae, Takeshi
2015-01-22 9:28 ` Loic Dachary
2015-01-22 16:34 ` Miyamae, Takeshi
2015-01-22 17:29 ` Loic Dachary
2015-01-23 1:16 ` Miyamae, Takeshi
2015-01-23 9:08 ` Loic Dachary
2015-01-23 12:47 ` Miyamae, Takeshi
2015-01-23 13:38 ` Loic Dachary
2015-01-24 15:52 ` Miyamae, Takeshi
2015-01-21 14:31 ` Loic Dachary
2015-01-23 13:46 ` Loic Dachary
2015-01-26 5:43 ` Miyamae, Takeshi
2015-01-26 11:02 ` Loic Dachary [this message]
2015-01-26 8:00 ` Miyamae, Takeshi
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=54C61ED5.5040603@dachary.org \
--to=loic@dachary.org \
--cc=ceph-devel@vger.kernel.org \
--cc=miyamae.takeshi@jp.fujitsu.com \
--cc=nakao.takanori@jp.fujitsu.com \
--cc=shiozawa.kennsu@jp.fujitsu.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.