linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Sterba <dsterba@suse.cz>
To: Chris Murphy <lists@colorremedies.com>
Cc: David Sterba <dsterba@suse.cz>, Nick Terrell <terrelln@fb.com>,
	Adam Borowski <kilobyte@angband.pl>,
	"dsterba@suse.com" <dsterba@suse.com>,
	"linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: [PATCH preview] btrfs: allow to set compression level for zlib
Date: Fri, 15 Sep 2017 16:51:16 +0200	[thread overview]
Message-ID: <20170915145116.GZ29043@twin.jikos.cz> (raw)
In-Reply-To: <CAJCQCtRsTSypEVx7iVG+TCojqL30Q15xZH2PYiZq3HdqLqwa9A@mail.gmail.com>

On Sun, Aug 20, 2017 at 06:38:50PM -0600, Chris Murphy wrote:
> On Fri, Aug 18, 2017 at 10:08 AM, David Sterba <dsterba@suse.cz> wrote:
> 
> > That's quite a lot, in kernel. IIRC zlib and lzo use less than 200kb,
> > zstd wants 800kb for level 1. And this needs to be contiguous memory, so
> > if we're lucky and get the memory at the mount time, fine. In general
> > the memory can be fragmented (in the worst case, there are only 4k
> > chunks available), so we'd have to vmalloc and consume the virtual,
> > mappings in great numbers.
> 
> Any thoughts on bootloader support, both in general, and as it relates
> to levels of compression and memory constraints? GRUB switches to
> protected mode early on but other bootloaders might have more
> limitations. I guess really it's just GRUB and extlinux right now,
> there were patches some time ago for Das U-Boot but they still aren't
> merged.

I'm not sure if the memory requirements are same for compression and
decompression. The table is related to compression. I've looked around
web to find what the decompression requirements are but havne't found
anything.

  reply	other threads:[~2017-09-15 14:52 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <<20170724172939.24527-1-dsterba@suse.com>
2017-08-04 21:51 ` [PATCH preview] btrfs: allow to set compression level for zlib Nick Terrell
2017-08-05  1:27   ` Adam Borowski
2017-08-05  2:15     ` Nick Terrell
2017-08-18 16:08       ` David Sterba
2017-08-21  0:38         ` Chris Murphy
2017-09-15 14:51           ` David Sterba [this message]
2017-09-15 18:13             ` Nick Terrell
2017-08-18 15:55   ` David Sterba
2017-07-24 17:29 David Sterba
2017-07-27  7:52 ` Anand Jain
2017-07-27 16:49   ` David Sterba

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20170915145116.GZ29043@twin.jikos.cz \
    --to=dsterba@suse.cz \
    --cc=dsterba@suse.com \
    --cc=kilobyte@angband.pl \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=lists@colorremedies.com \
    --cc=terrelln@fb.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).