public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: David Sterba <dsterba@suse.cz>
To: Roger Binns <rogerb@rogerbinns.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: Working on Btrfs as topic for master thesis
Date: Wed, 22 Jan 2014 13:12:20 +0100	[thread overview]
Message-ID: <20140122121220.GF6498@twin.jikos.cz> (raw)
In-Reply-To: <lbid3r$1ui$1@ger.gmane.org>

On Sun, Jan 19, 2014 at 09:44:39PM -0800, Roger Binns wrote:
> If you are more interested in the theoretical side then looking into
> compression would be interesting.  ie how close to the theoretical best
> compression are we.  Various filesystems like btrfs and NTFS make all
> sorts of compromises in algorithm choices but also especially in the size
> of blocks they compress.  How much better could be done?

I have done some work here, so far it's stalled due to more important
work.

https://btrfs.wiki.kernel.org/index.php/Project_ideas#Compression_enhancements

Do you have other suggestions beyond what's proposed there?

  reply	other threads:[~2014-01-22 12:12 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-16 19:23 Working on Btrfs as topic for master thesis Toggenburger Lukas
2014-01-17 15:34 ` David Sterba
2014-01-17 16:04 ` Tomasz Torcz
2014-01-18 12:50   ` Toggenburger Lukas
2014-01-22 12:05     ` David Sterba
2014-01-22 13:35       ` Hugo Mills
2014-01-20  5:44 ` Roger Binns
2014-01-22 12:12   ` David Sterba [this message]
2014-01-22 20:55     ` Roger Binns
2014-01-23 18:36       ` David Sterba
2014-01-23 21:47         ` Roger Binns
2014-01-20 12:20 ` Austin S Hemmelgarn
2014-01-21  6:42   ` Sandy McArthur
2014-01-21 12:25     ` Austin S Hemmelgarn
2014-01-21 16:52       ` Hugo Mills
2014-01-21 16:59         ` Austin S Hemmelgarn
2014-01-22 12:20         ` David Sterba
2014-01-22 12:24           ` 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=20140122121220.GF6498@twin.jikos.cz \
    --to=dsterba@suse.cz \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=rogerb@rogerbinns.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