From: Gordan Bobic <gordan@bobich.net>
To: reiserfs-devel@vger.kernel.org
Subject: Re: reiser4 mkfs, cryptcompress, tail packing, etc.
Date: Tue, 24 Aug 2010 20:14:10 +0100 [thread overview]
Message-ID: <4C741A02.3090004@bobich.net> (raw)
In-Reply-To: <4C7405CF.3040609@gmail.com>
On 08/24/2010 06:47 PM, Edward Shishkin wrote:
>> Also, is there a nolog option on reiser4 as there is on reiserfs?
>
> no sorry, currently reiser4 transaction manager can not be switched off.
Is there a way to use an external journal and point it at a different
device (e.g. ramdisk/tmpfs), and force fsck on unclean shutdown instead?
>> 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?
>
> Works as usual: when populating address space by readpage(s) data are
> read from disk and decompressed.
> If page gets dirty, then its data will be compressed in flush time and
> written to disk.
What about the hard-link issue I mentioned? If two hard-links point to
the same inode with a compressed shared library, will it work as
expected and only map the file into shared memory once even if both .so
files are dyna-linked by different running binaries?
Gordan
next prev parent reply other threads:[~2010-08-24 19:14 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 [this message]
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=4C741A02.3090004@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.