From: Jeff Mahoney <jeffm@suse.com>
To: Michael Weissenbacher <webmaster@dermichi.com>
Cc: reiserfs-list@namesys.com
Subject: Re: quicker mount
Date: Thu, 27 Apr 2006 11:41:48 -0400 [thread overview]
Message-ID: <4450E63C.5080306@suse.com> (raw)
In-Reply-To: <4450DBDB.5060209@dermichi.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Michael Weissenbacher wrote:
> Hi,
>> It takes so long to mount since ReiserFS reads all the bitmaps before
>> mounting. The larger the file system, the longer it takes.
> I wonder why it has to read all of them. Are they stored in RAM after
> reading? Otherwise I cannot see why it should be done at all.
Yes, they're kept in RAM. You can see the debate on this in the list
archives, but I asked the same questions.
There is no reason for the bitmaps to be retained in memory, as they're
more rarely used than other metadata which simply relys on the kernel to
cache intelligently.
The patches are written, they just need some debugging. Unfortunately,
they're kind of on the back burner right now due to other work constraints.
- -Jeff
- --
Jeff Mahoney
SUSE Labs
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFEUOY8LPWxlyuTD7IRAguzAKCiudFGY1tFXOiSJ1743lrrb5kBJgCfcVG/
a3YBOD1EVcrEGsDFgkWRkKs=
=9lHG
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2006-04-27 15:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-27 14:36 quicker mount Andrea Gelmini
2006-04-27 14:42 ` Jeff Mahoney
2006-04-27 14:57 ` Michael Weissenbacher
2006-04-27 15:41 ` Jeff Mahoney [this message]
2006-05-01 20:39 ` Jeff Mahoney
2006-05-02 3:47 ` Jeff Mahoney
2006-05-23 14:43 ` Tom Vier
2006-05-23 16:07 ` Vladimir V. Saveliev
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=4450E63C.5080306@suse.com \
--to=jeffm@suse.com \
--cc=reiserfs-list@namesys.com \
--cc=webmaster@dermichi.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.