From: Goffredo Baroncelli <kreijack@gmail.com>
To: Tomasz Torcz <tomek@pipebreaker.pl>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: Mounting raid without a btrfsctl scan
Date: Sun, 16 May 2010 20:44:23 +0200 [thread overview]
Message-ID: <201005162044.23272.kreijack@libero.it> (raw)
In-Reply-To: <AANLkTinRVuk_uJBLsBD0ANdKkEHs-9zz4Tor_0xi7oCI@mail.gmail.com>
On Sunday 16 May 2010, Sebastian 'gonX' Jensen wrote:
> On 16 May 2010 02:02, Tomasz Torcz <tomek@pipebreaker.pl> wrote:
[...]
> I don't know if I mentioned it before, but my system
> spends at least 6 seconds in the initramfs before passing control over
> to my distributions initscripts. Part of it is obviously because of
> btrfs having to spend approximately 3 seconds probing for devices (I
> have a decent amount of devices).
> However, btrfs does not have that
> many functions yet. Would it be possible to at least have partial
> functionality kernel side, so that an initramfs is not required for
> mounting RAID devices?
I think that the good question is: why a kernel probing should be faster than
a user space probing ?
I think that some reasons of the time required by the btrfsctl scan in user
space are:
1) a scan performed via 'btrfsctl -a' scans every block device (cdrom and
floppy included). I suggest to perform a scan via udev (see my previous post);
that should be reduce the boot time.
2) the actual initramfs tools pay attention to wait that _all_ devices
appeared. This requires a bit of time which is not related to the "user space"
scan.
Comments ?
G.Baroncelli
>
> > --
> > Tomasz Torcz ,,If you try to upissue this patchset I shall be
seeking
> > xmpp: zdzichubg@chrome.pl an IP-routable hand grenade.'' -- Andrew
Morton (LKML)
> >
> > --
> > To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
> > the body of a message to majordomo@vger.kernel.org
> > More majordomo info at http://vger.kernel.org/majordomo-info.html
> >
> --
> To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
--
gpg key@ keyserver.linux.it: Goffredo Baroncelli (ghigo) <kreijackATinwind.it>
Key fingerprint = 4769 7E51 5293 D36C 814E C054 BF04 F161 3DC5 0512
next prev parent reply other threads:[~2010-05-16 18:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-15 11:11 Mounting raid without a btrfsctl scan Matt Brown
2010-05-15 14:36 ` Goffredo Baroncelli
2010-05-15 16:47 ` Sebastian 'gonX' Jensen
2010-05-16 0:02 ` Tomasz Torcz
2010-05-16 0:41 ` Sebastian 'gonX' Jensen
2010-05-16 18:44 ` Goffredo Baroncelli [this message]
2010-05-16 19:38 ` Sebastian 'gonX' Jensen
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=201005162044.23272.kreijack@libero.it \
--to=kreijack@gmail.com \
--cc=kreijack@libero.it \
--cc=linux-btrfs@vger.kernel.org \
--cc=tomek@pipebreaker.pl \
/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).