From: David Masover <ninja@slaphack.com>
To: "Pierre Etchemaïté" <petchema@concept-micro.com>
Cc: reiserfs-list@namesys.com
Subject: Re: [PATCH] reiserfs: on-demand bitmap loading (testing only)
Date: Thu, 07 Jul 2005 18:15:56 -0500 [thread overview]
Message-ID: <42CDB7AC.8030408@slaphack.com> (raw)
In-Reply-To: <20050708003756.21bd4c80.petchema@concept-micro.com>
Pierre Etchemaïté wrote:
> Le Thu, 7 Jul 2005 13:59:35 -0400, studdugie <studdugie@gmail.com> a écrit :
>
>
>>I agree w/ Jeff 100%. I'm not a kernel hacker, simply a user. As a
>>matter of fact, I was one of those people that Jeff aluded to when he
>>said: "There have been reports of large filesystems taking an
>>unacceptably long time to mount."
>
>
> That also makes reiserfs uncomfortable with automount devices, specially
> if they're bandwidth limited like external USB or firewire disks...
USB and firewire disks already take a little long to mount anyway.
But, it is definitely a performance enhancement, or at least a tweak.
I'd like to see it happen -- it takes 10-15 seconds to mount my 200 gig
Reiser4 partition, which is unacceptabe for a desktop machine -- at
least, for a *linux* desktop machine.
To keep Hans happy about the "default case", can we load the bitmap in
the background during boot/mount? Basically, if it's loaded on demand,
then we pretend to demand each part of it, one by one. Would that
considerably slow normal FS operation? Could we defer it to when the
disk is idle? (*disk*, not FS)
next prev parent reply other threads:[~2005-07-07 23:15 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-06 21:22 [PATCH] reiserfs: on-demand bitmap loading (testing only) Jeff Mahoney
2005-07-06 22:45 ` Hans Reiser
2005-07-07 16:04 ` Jeff Mahoney
2005-07-07 17:59 ` studdugie
2005-07-07 22:37 ` Pierre Etchemaïté
2005-07-07 23:15 ` David Masover [this message]
2005-07-08 4:52 ` Jeffrey Mahoney
2005-07-08 5:52 ` Stefan Traby
2005-07-08 16:55 ` David Masover
2005-07-08 21:41 ` Jeff Mahoney
2005-07-09 7:46 ` Hans Reiser
2005-07-08 5:35 ` Alexander Zarochentsev
2005-07-08 6:04 ` Stefan Traby
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=42CDB7AC.8030408@slaphack.com \
--to=ninja@slaphack.com \
--cc=petchema@concept-micro.com \
--cc=reiserfs-list@namesys.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.