Re: v2 aligned buffer changes for erasure codes

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi,

On 2014-09-18 12:18:59 +0000, Andreas Joachim Peters wrote:
> 
> => (src/erasure-code/isa/README claims it needs 16*k byte aligned buffers
> 
> I should update the README since it is misleading ... it should say 
> 8*k or 16*k byte aligned chunk size depending on the compiler/platform 
> used, it is not the alignment of the allocated buffer addresses.The 
> get_alignment in the plug-in function is used to compute the chunk 
> size for the encoding (as I said not the start address alignment). 

I've seen that

> If you pass k buffers for decoding each buffer should be aligned at 
> least to 16 or as you pointed out better 32 bytes. 

ok, that makes sense

> For encoding there is normally a single buffer split 'virtually' into 
> k pieces. To make all pieces starting at an aligned address one needs 
> to align the chunk size to e.g. 16*k.

I don't get that. How is the buffer splitted? into k (+ m) chunk size 
parts? As long as the start and the length are both 16 (or 32) byte 
aligned all parts are properly aligned too. I don't see where the k 
comes into play.

cheers

Janne
--
To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html




[Index of Archives]     [CEPH Users]     [Ceph Large]     [Information on CEPH]     [Linux BTRFS]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]
  Powered by Linux