CEPH filesystem development
 help / color / mirror / Atom feed
* Locally Repairable Codes vs Pyramid
@ 2014-06-02 16:00 Loic Dachary
  2014-06-05 14:00 ` Loic Dachary
  0 siblings, 1 reply; 2+ messages in thread
From: Loic Dachary @ 2014-06-02 16:00 UTC (permalink / raw)
  To: Ceph Development; +Cc: Dan Lambright, Xavier Hernandez

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

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 --]

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2014-06-05 14:00 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2014-06-02 16:00 Locally Repairable Codes vs Pyramid Loic Dachary
2014-06-05 14:00 ` Loic Dachary

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox