From: Edward Shishkin <edward.shishkin@gmail.com>
To: Gordan Bobic <gordan@bobich.net>
Cc: reiserfs-devel@vger.kernel.org
Subject: Re: reiser4 mkfs, cryptcompress, tail packing, etc.
Date: Tue, 24 Aug 2010 21:21:00 +0200 [thread overview]
Message-ID: <4C741B9C.5070302@gmail.com> (raw)
In-Reply-To: <4C7405CF.3040609@gmail.com>
Edward Shishkin wrote:
> Gordan Bobic wrote:
>> Hi,
>
> Hello.
>
>>
>> It's been a while since I last tried reiser4, and having just looked
>> at the wiki, I couldn't find any info at all on the cryptocompress
>> plugin and tail packing options at mkfs time specifically relating to
>> reiser4.
>
> mkfs.reiser4 -l:
>
> compression modes (works "per file"):
>
> "latt" (id:0x1 type:0xd) ['Check on dynamic lattice'
> compression mode plugin.]
> If logical cluster in incompressible, then switch compression off and
> check every
> K-th cluster, where K dynamically increased to 32 on every non-success
> after
> compression. If cluster is compressible, than K is set back to 1, etc..
>
> "ultim" (id:0x2 type:0xd) ['Check ultimately' compression
> mode plugin.]
> Switch compression off forever after the first case of non-success.
>
> "force" (id:0x3 type:0xd) ['Compress evrything'
> compression mode plugin.]
> Force to compress everything.
>
> "conv" (id:0x4 type:0xd) ['Convert to extent' compression
> mode plugin.]
> If the first logical cluster of the file is incompressible, then
> switch compression off forever.
Sorry, this is not everything. Here should also go "otherwise switch to
"latt" mode
(see above)".
So not everything is bad for media-files in this mode.
prev parent reply other threads:[~2010-08-24 19:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-24 16:06 reiser4 mkfs, cryptcompress, tail packing, etc Gordan Bobic
2010-08-24 17:47 ` Edward Shishkin
2010-08-24 17:56 ` Edward Shishkin
2010-08-24 19:14 ` Gordan Bobic
2010-08-24 19:39 ` Edward Shishkin
2010-08-24 19:21 ` Edward Shishkin [this message]
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=4C741B9C.5070302@gmail.com \
--to=edward.shishkin@gmail.com \
--cc=gordan@bobich.net \
--cc=reiserfs-devel@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;
as well as URLs for NNTP newsgroup(s).