Re: [PATCH 6/7] lib/lzo: implement run-length encoding
On (11/29/18 12:08), Sergey Senozhatsky wrote: > On (11/27/18 16:19), Dave Rodgman wrote: > > > > This modifies the bitstream in a way which is backwards compatible > > (i.e., we can decompress old bitstreams, but old versions of lzo > > cannot decompress new bitstreams). > > > > Hmmm... Whoa. Help me understand this: > > So a btrfs filesystem, compressed with the new lzo, say I run 4.21, > won't be readable at all once I reboot under 4.19? > > What about compressed net traffic between servers running different > kernel version (one with new lzo, the other one with old lzo)? > XFRM can be compressed with lzo, can't it? Ah, false alarm. Sorry for the noise! You create a new lzo version in the next patch. -ss
Re: [PATCH 6/7] lib/lzo: implement run-length encoding
On (11/29/18 12:08), Sergey Senozhatsky wrote: > On (11/27/18 16:19), Dave Rodgman wrote: > > > > This modifies the bitstream in a way which is backwards compatible > > (i.e., we can decompress old bitstreams, but old versions of lzo > > cannot decompress new bitstreams). > > > > Hmmm... Whoa. Help me understand this: > > So a btrfs filesystem, compressed with the new lzo, say I run 4.21, > won't be readable at all once I reboot under 4.19? > > What about compressed net traffic between servers running different > kernel version (one with new lzo, the other one with old lzo)? > XFRM can be compressed with lzo, can't it? Ah, false alarm. Sorry for the noise! You create a new lzo version in the next patch. -ss
Re: [PATCH 6/7] lib/lzo: implement run-length encoding
On (11/27/18 16:19), Dave Rodgman wrote: > > This modifies the bitstream in a way which is backwards compatible > (i.e., we can decompress old bitstreams, but old versions of lzo > cannot decompress new bitstreams). > Hmmm... Whoa. Help me understand this: So a btrfs filesystem, compressed with the new lzo, say I run 4.21, won't be readable at all once I reboot under 4.19? What about compressed net traffic between servers running different kernel version (one with new lzo, the other one with old lzo)? XFRM can be compressed with lzo, can't it? -ss
Re: [PATCH 6/7] lib/lzo: implement run-length encoding
On (11/27/18 16:19), Dave Rodgman wrote: > > This modifies the bitstream in a way which is backwards compatible > (i.e., we can decompress old bitstreams, but old versions of lzo > cannot decompress new bitstreams). > Hmmm... Whoa. Help me understand this: So a btrfs filesystem, compressed with the new lzo, say I run 4.21, won't be readable at all once I reboot under 4.19? What about compressed net traffic between servers running different kernel version (one with new lzo, the other one with old lzo)? XFRM can be compressed with lzo, can't it? -ss
