Skip to content

Commit 9fd2b85

Browse files
authored
Merge pull request ceph#60508 from zdover23/wip-doc-2024-10-27-rados-operations-erasure-code-jerasure
doc/rados: add blaum_roth coding guidance Reviewed-by: Anthony D'Atri <[email protected]>
2 parents db181e5 + 6648d94 commit 9fd2b85

File tree

1 file changed

+18
-0
lines changed

1 file changed

+18
-0
lines changed

doc/rados/operations/erasure-code-jerasure.rst

Lines changed: 18 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -60,6 +60,24 @@ Where:
6060
*blaum_roth*, *liber8tion* are *RAID6* equivalents in
6161
the sense that they can only be configured with *m=2*.
6262

63+
.. note:: When using ``blaum_roth`` coding, the default
64+
word size of ``w=7`` is suboptimal because ``blaum_roth``
65+
works best when ``w+1`` is prime. When creating a new
66+
erasure-code profile with ``technique=blaum_roth``,
67+
set ``w`` to a number that is one integer less than a prime
68+
number (for example, ``6``). See `Loic Dachary's
69+
commit f51d21b to ceph/ceph <https://github.com/ceph/ceph/commit/f51d21b53d26d4f27c950cb1ba3f989e713ab325>`_ for information about
70+
why this default cannot be changed easily in the
71+
source code, and see `the second bullet point on
72+
page 29 of Plank and Greenan's "Jerasure: A Library
73+
in C Facilitating Erasure Coding for Storage
74+
Applications" <https://github.com/ceph/jerasure/blob/master/Manual.pdf>`_ for an unequivocal statement of the restriction that applies
75+
to ``w`` when using Blaum-Roth coding.
76+
(Information about the proper value of ``w`` when
77+
using ``blaum_roth`` coding was provided to the
78+
Ceph upstream in September of 2024 by Benjamin
79+
Mare.)
80+
6381
:Type: String
6482
:Required: No.
6583
:Default: reed_sol_van

0 commit comments

Comments
 (0)