From: Zan Lynx <zlynx@acm.org>
To: stevenaaus@yahoo.com
Cc: reiserfs-devel@vger.kernel.org
Subject: Re: Hi Reiserfs-dev
Date: Tue, 26 Aug 2008 18:46:01 -0600 [thread overview]
Message-ID: <48B4A3C9.2090508@acm.org> (raw)
In-Reply-To: <325143.47271.qm@web53207.mail.re2.yahoo.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Steven wrote:
> Been using Reiser 3 for years now, messing round with m-multiple
> operating systems. Imho, it's easily the best general purpose linux
> filesystem. Does anyone here say otherwise ?
>
> I went through the hassle of installing reiser 4 on 2.6.24 about a
> year ago, but it seemed to have latency issues, esp. at start-up
> (fedora 4, 1.13 PIII dell laptop with 256ram) and reverted back to
> reiser 3. Ideas?
>
> Thanks, Steven.
I've been running Reiser4 on my laptop as / for a long time now. I have
two bits of advice.
Make sure it mounts at boot with the noatime option. Something like
"rootflags=noatime" on your LILO or GRUB kernel options line.
Have your init scripts set the queue depth on your block IO scheduler to
1024. Something like "echo 1024 > /sys/block/sda/queue/nr_requests".
With just 256 MB you might want to try smaller values. I'm not very
clear on how much RAM each queue slot can use.
I found that Reiser4 will appear to hang if it cannot flush an entire
transaction atom to the IO queue in one go. Make sure it's big enough.
The other thing that seems to make it a little slow is that it uses
barriers. This is a Linux feature that serious filesystems use to
guarantee data integrity. ext3 uses barriers for its journal and XFS
uses barriers too. I believe there were patches for reiser3 to use
barriers too but I don't know if those are in all Linux or just SUSE.
As I understand it, on an IDE drive, a barrier is pretty slow because it
forces a full write queue flush, does the write, then flushes the queue
*again* before continuing. On a real SCSI device with tagged queuing
this works much more quickly because it can continue to issue disk
commands after the barrier.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.8 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iEYEARECAAYFAki0o8gACgkQolqWs/Y4NLy9MgCgh3v5mB4uLx673JT1sz6dgJyA
1XEAni0AZxC6DokBQQ+sDu18qbzxP0s5
=K2Cy
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2008-08-27 0:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-27 0:11 Hi Reiserfs-dev Steven
2008-08-27 0:46 ` Zan Lynx [this message]
2008-08-27 4:48 ` Volker Armin Hemmann
2008-08-28 1:29 ` Steven
2008-08-28 17:36 ` Edward Shishkin
2008-09-01 1:20 ` Steven
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=48B4A3C9.2090508@acm.org \
--to=zlynx@acm.org \
--cc=reiserfs-devel@vger.kernel.org \
--cc=stevenaaus@yahoo.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 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.