CEPH filesystem development
 help / color / mirror / Atom feed
From: Loic Dachary <loic@dachary.org>
To: Ceph Development <ceph-devel@vger.kernel.org>
Subject: Re: Locally Repairable Codes vs Pyramid
Date: Thu, 05 Jun 2014 16:00:50 +0200	[thread overview]
Message-ID: <53907812.6030100@dachary.org> (raw)
In-Reply-To: <538C9FA2.3020805@dachary.org>

[-- Attachment #1: Type: text/plain, Size: 1115 bytes --]

For the record and since nobody objected, I made the suggested change.

On 02/06/2014 18:00, Loic Dachary wrote:
> Hi Ceph,
> 
> TL;DR: s/pyramid/LRC/ in the implementation of http://pad.ceph.com/p/cdsgiant-pyramid-erasure-code for clarity
> 
> Although the term "Pyramid code" has been consistently used in reference to the technique used to reduce the network requirements when repairing from the loss of a single OSD (put simply ;-), I realized today when discussing with Dan Lambright and Xavier Hernandez from glusterfs that I was unclear about what it really means.
> 
> As far as I can tell, LRC as described in http://anrg.usc.edu/~maheswaran/Xorbas.pdf suggests an implementation that is close to what has been described during the last CDS. In contrast the pyramid code paper http://research.microsoft.com/pubs/70415/tr-2007-25.pdf suggests a more sophisticated approach which I do not fully understand. 
> 
> Instead of hardcoding the word "pyramid" in the pathnames of the implementation it seems better to use "LRC" instead.
> 
> Cheers
> 

-- 
Loïc Dachary, Artisan Logiciel Libre


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 263 bytes --]

      reply	other threads:[~2014-06-05 14:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-02 16:00 Locally Repairable Codes vs Pyramid Loic Dachary
2014-06-05 14:00 ` Loic Dachary [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=53907812.6030100@dachary.org \
    --to=loic@dachary.org \
    --cc=ceph-devel@vger.kernel.org \
    /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