On Tue, Nov 13, 2018 at 01:33:32AM +0100, David Sterba wrote:
> On Wed, Oct 31, 2018 at 11:11:08AM -0700, Nick Terrell wrote:
> > From: Jennifer Liu
> >
> > Adds zstd compression level support to btrfs. Zstd requires
> > different amounts of memory for ea
0, Nick Terrell wrote:
> > >> From: Jennifer Liu
> > >>
> > >> Adds zstd compression level support to btrfs. Zstd requires
> > >> different amounts of memory for each level, so the design had
> > >> to be modified to allow set_level() to allocate memory
> On Nov 13, 2018, at 5:29 AM, Timofey Titovets wrote:
>
> вт, 13 нояб. 2018 г. в 04:52, Nick Terrell :
>>
>>
>>
>>> On Nov 12, 2018, at 4:33 PM, David Sterba wrote:
>>>
>>> On Wed, Oct 31, 2018 at 11:11:08AM -0700, Nick Terrel
вт, 13 нояб. 2018 г. в 04:52, Nick Terrell :
>
>
>
> > On Nov 12, 2018, at 4:33 PM, David Sterba wrote:
> >
> > On Wed, Oct 31, 2018 at 11:11:08AM -0700, Nick Terrell wrote:
> >> From: Jennifer Liu
> >>
> >> Adds zstd compression level
> On Nov 12, 2018, at 4:33 PM, David Sterba wrote:
>
> On Wed, Oct 31, 2018 at 11:11:08AM -0700, Nick Terrell wrote:
>> From: Jennifer Liu
>>
>> Adds zstd compression level support to btrfs. Zstd requires
>> different amounts of memory for each level, so
On Wed, Oct 31, 2018 at 11:11:08AM -0700, Nick Terrell wrote:
> From: Jennifer Liu
>
> Adds zstd compression level support to btrfs. Zstd requires
> different amounts of memory for each level, so the design had
> to be modified to allow set_level() to allocate memory. We
&g
On Wed, Oct 31, 2018 at 11:11:08AM -0700, Nick Terrell wrote:
> From: Jennifer Liu
>
> Adds zstd compression level support to btrfs. Zstd requires
> different amounts of memory for each level, so the design had
> to be modified to allow set_level() to allocate memory. We
&g
> On Nov 1, 2018, at 5:57 AM, Timofey Titovets wrote:
>
> ср, 31 окт. 2018 г. в 21:12, Nick Terrell :
>>
>> From: Jennifer Liu
>>
>> Adds zstd compression level support to btrfs. Zstd requires
>> different amounts of memory for each level, so th
ср, 31 окт. 2018 г. в 21:12, Nick Terrell :
>
> From: Jennifer Liu
>
> Adds zstd compression level support to btrfs. Zstd requires
> different amounts of memory for each level, so the design had
> to be modified to allow set_level() to allocate memory. We
> prea
From: Jennifer Liu
Adds zstd compression level support to btrfs. Zstd requires
different amounts of memory for each level, so the design had
to be modified to allow set_level() to allocate memory. We
preallocate one workspace of the maximum size to guarantee
forward progress. This feature
On Tue, Oct 30, 2018 at 12:06:21PM -0700, Nick Terrell wrote:
> From: Jennifer Liu
>
> Adds zstd compression level support to btrfs. Zstd requires
> different amounts of memory for each level, so the design had
> to be modified to allow set_level() to allocate memory. We
&g
From: Jennifer Liu
Adds zstd compression level support to btrfs. Zstd requires
different amounts of memory for each level, so the design had
to be modified to allow set_level() to allocate memory. We
preallocate one workspace of the maximum size to guarantee
forward progress. This feature
On Tue, May 15, 2018 at 04:51:26PM +0900, Misono Tomohiro wrote:
> Incompat flag of lzo/zstd compression should be set at:
> 1. mount time (-o compress/compress-force)
> 2. when defrag is done
> 3. when property is set
>
> Currently 3. is missing and this commit adds this
On 05/15/2018 04:35 PM, Duncan wrote:
> Su Yue posted on Tue, 15 May 2018 16:05:01 +0800 as excerpted:
>
>
>>
>> On 05/15/2018 03:51 PM, Misono Tomohiro wrote:
>>> Incompat flag of lzo/zstd compression should be set at:
>>> 1. mount time (-o compr
Su Yue posted on Tue, 15 May 2018 16:05:01 +0800 as excerpted:
>
> On 05/15/2018 03:51 PM, Misono Tomohiro wrote:
>> Incompat flag of lzo/zstd compression should be set at:
>> 1. mount time (-o compress/compress-force)
>> 2. when defrag is done 3. when property i
On 05/15/2018 04:05 PM, Su Yue wrote:
>
>
> On 05/15/2018 03:51 PM, Misono Tomohiro wrote:
>> Incompat flag of lzo/zstd compression should be set at:
>> 1. mount time (-o compress/compress-force)
>> 2. when defrag is done
>> 3. when property is
On 05/15/2018 03:51 PM, Misono Tomohiro wrote:
Incompat flag of lzo/zstd compression should be set at:
1. mount time (-o compress/compress-force)
2. when defrag is done
3. when property is set
Currently 3. is missing and this commit adds this.
Signed-off-by: Tomohiro Misono
On 05/15/2018 03:51 PM, Misono Tomohiro wrote:
> Incompat flag of lzo/zstd compression should be set at:
> 1. mount time (-o compress/compress-force)
> 2. when defrag is done
> 3. when property is set
>
> Currently 3. is missing and this commit adds this.
>
If
Incompat flag of lzo/zstd compression should be set at:
1. mount time (-o compress/compress-force)
2. when defrag is done
3. when property is set
Currently 3. is missing and this commit adds this.
Signed-off-by: Tomohiro Misono <misono.tomoh...@jp.fujitsu.com>
---
fs/btrfs/props.
2017-11-16 19:32 GMT+03:00 Austin S. Hemmelgarn :
> On 2017-11-16 08:43, Duncan wrote:
>>
>> Austin S. Hemmelgarn posted on Thu, 16 Nov 2017 07:30:47 -0500 as
>> excerpted:
>>
>>> On 2017-11-15 16:31, Duncan wrote:
Austin S. Hemmelgarn posted on Wed, 15 Nov 2017
On 2017-11-16 08:43, Duncan wrote:
Austin S. Hemmelgarn posted on Thu, 16 Nov 2017 07:30:47 -0500 as
excerpted:
On 2017-11-15 16:31, Duncan wrote:
Austin S. Hemmelgarn posted on Wed, 15 Nov 2017 07:57:06 -0500 as
excerpted:
The 'compress' and 'compress-force' mount options only impact newly
Austin S. Hemmelgarn posted on Thu, 16 Nov 2017 07:30:47 -0500 as
excerpted:
> On 2017-11-15 16:31, Duncan wrote:
>> Austin S. Hemmelgarn posted on Wed, 15 Nov 2017 07:57:06 -0500 as
>> excerpted:
>>
>>> The 'compress' and 'compress-force' mount options only impact newly
>>> written data. The
On 11/16/17, Austin S. Hemmelgarn wrote:
> I'm pretty sure defrag is equivalent to 'compress-force', not
> 'compress', but I may be wrong.
Are there any devs to confirm this?
--
To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
the body of a message
On 2017-11-15 16:31, Duncan wrote:
Austin S. Hemmelgarn posted on Wed, 15 Nov 2017 07:57:06 -0500 as
excerpted:
The 'compress' and 'compress-force' mount options only impact newly
written data. The compression used is stored with the metadata for the
extents themselves, so any existing data
Austin S. Hemmelgarn posted on Wed, 15 Nov 2017 07:57:06 -0500 as
excerpted:
> The 'compress' and 'compress-force' mount options only impact newly
> written data. The compression used is stored with the metadata for the
> extents themselves, so any existing data on the volume will be read just
>
On 2017-11-15 05:35, Imran Geriskovan wrote:
On 11/15/17, Lukas Pirl wrote:
you might be interested in the thread "Read before you deploy
btrfs + zstd"¹.
Thanks. I've read it. Bootloader is not an issue since /boot is on
another uncompressed fs.
Let me make my question
On 11/15/17, Lukas Pirl wrote:
> you might be interested in the thread "Read before you deploy
> btrfs + zstd"¹.
Thanks. I've read it. Bootloader is not an issue since /boot is on
another uncompressed fs.
Let me make my question more generic:
Can there be any issues for
Hi Imran,
On 11/15/2017 09:51 AM, Imran Geriskovan wrote as excerpted:
> Any further advices?
you might be interested in the thread "Read before you deploy btrfs +
zstd"¹.
Cheers,
Lukas
¹ https://www.mail-archive.com/linux-btrfs@vger.kernel.org/msg69871.html
--
To unsubscribe from this list:
Kernel 4.14 now includes btrfs zstd compression support.
My question:
I currently have a fs mounted and used with "compress=lzo"
option. What happens if I change it to "compress=zstd"?
My guess is that existing files will be read and uncompressed via lzo.
And new files will
29 matches
Mail list logo