From: Gordan Bobic <gordan@bobich.net>
To: reiserfs-devel@vger.kernel.org
Subject: reiser4 mkfs, cryptcompress, tail packing, etc.
Date: Tue, 24 Aug 2010 17:06:07 +0100 [thread overview]
Message-ID: <4C73EDEF.8020701@bobich.net> (raw)
Hi,
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.
Also, is there a nolog option on reiser4 as there is on reiserfs?
The reason I ask is because I am looking for a file system that improves
on ext2 for very slow writing flash media (think cheap USB sticks, SD
cards, etc.). So, ideally, I want to disable journalling and enable
compression, to minimize the number of writing to the underlying media.
In theory, compression with journalling switched off should give reiser4
an edge in this use-case, so I just wanted to check what the current
state of the compression is (couldn't find any references to -o
create=ccreg40 in the wiki), and that it works as one might expect
(compressing before committing to disk).
Another question (not sure if it is specifically related to reiser4 or
generic) is about compressed hard-linked DLLs and mmap. Specifically, if
a .so is hard-linked in two places, dynamically linking to each instance
causes both to be mmapped to the same memory since they'll have the same
inode, and that means the memory is only used once. How does this work
if the .so is compressed? Does it all still work the same, with the
decompressed file being in a single mmap for both dynamically linked
instances?
Many thanks.
Gordan
next reply other threads:[~2010-08-24 16:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-24 16:06 Gordan Bobic [this message]
2010-08-24 17:47 ` reiser4 mkfs, cryptcompress, tail packing, etc 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
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=4C73EDEF.8020701@bobich.net \
--to=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).