public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Roger Binns <rogerb@rogerbinns.com>
To: linux-btrfs@vger.kernel.org
Subject: Re: Working on Btrfs as topic for master thesis
Date: Thu, 23 Jan 2014 13:47:17 -0800	[thread overview]
Message-ID: <lbs2kp$6km$1@ger.gmane.org> (raw)
In-Reply-To: <20140123183624.GQ6498@twin.jikos.cz>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 23/01/14 10:36, David Sterba wrote:
> 'Theoretical best' seems too vaguely defined,

It seems like a good thing for someone to tackle as part of a master's
thesis :-)

> with compression it's always some trade-off and compromise

Which you can put in context against the theoretical best.  The links you
gave are a good example of trying to do that.

> This is a bit different usecase, defrag is triggered by user at the
> time he knows the resources are available

I'm a user and I use autodefrag :-)  As a developer you are more
interested in making users be aware of what they do, when they do it, and
carefully select the optimum conditions and configuration.

As a user I just want to point to a pile of storage and have btrfs do the
right thing, without me having to babysit it or play admin.  Computers
have billions of processor cycles per second, gigabytes of memory etc.
They should just figure this stuff out and not require me to be versed in
lots of intricate details!

> Keeping the dictionary implies more data to be read/written, with
> small chunks there's a low chance of actual dictionary reuse for other
> files.

I'm willing to bet that there is a good chance of reuse for files with the
same extension as an example.  And it is highly likely for Maildir files.

> Also, thinking about the implementaion, it would become too complex to 
> do in kernel for this particular usecase.

A thesis could study if it is worth doing first.  If it found that was a
good idea, then figuring out how to implement it is a second step.

> "To Zip or Not to Zip: Effective Resource Usage for Real-Time 
> Compression"

Except for systems that are 100% busy all the time, there is no need to
get perfect real time compression.  IMHO it is fine coming back later and
doing a better job of it.  Again this assumes that there is a sufficiently
large difference between what real time does and what a later
recompression does.

Roger
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.14 (GNU/Linux)

iEYEARECAAYFAlLhjeUACgkQmOOfHg372QTBKwCgxbWmfwr0MMfAo9bVwThmGTOq
F1EAoIsgVlzfeqPZS9zpKM1mJ3Cdw9LL
=IINU
-----END PGP SIGNATURE-----


  reply	other threads:[~2014-01-23 21:47 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
2014-01-22 20:55     ` Roger Binns
2014-01-23 18:36       ` David Sterba
2014-01-23 21:47         ` Roger Binns [this message]
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='lbs2kp$6km$1@ger.gmane.org' \
    --to=rogerb@rogerbinns.com \
    --cc=linux-btrfs@vger.kernel.org \
    /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