From: Neil Brown <neilb@suse.de>
To: Ingo Molnar <mingo@elte.hu>
Cc: Arjan van de Ven <arjan@infradead.org>,
linux-kernel@vger.kernel.org, davej@redhat.com
Subject: Re: [PATCH] raid: make RAID autodetect default a KConfig option
Date: Tue, 23 Sep 2008 13:45:19 +1000 [thread overview]
Message-ID: <18648.26191.479291.883160@notabene.brown> (raw)
In-Reply-To: message from Ingo Molnar on Monday September 22
On Monday September 22, mingo@elte.hu wrote:
>
> * Arjan van de Ven <arjan@infradead.org> wrote:
>
> > From 812bf9a448d96375a3aec5c51764d74cace85abb Mon Sep 17 00:00:00 2001
> > From: Arjan van de Ven <arjan@linux.intel.com>
> > Date: Sun, 21 Sep 2008 15:44:32 -0700
> > Subject: [PATCH] raid: make RAID autodetect default a KConfig option
> >
> > RAID autodetect has the side effect of requiring synchronisation of
> > all device drivers, which can make the boot several seconds longer
> > (I've measured 7 on one of my laptops).... even for systems that don't
> > have RAID setup for the root filesystem (the only FS where this
> > matters).
> >
> > This patch makes the default for autodetect a config option; either
> > way the user can always override via the kernel command line.
>
> Neil, if you agree with this patch, could you please send your Acked-by
> line? This patch depends on a clean-up in init/do_mounts_md.c that is in
> the fastboot tree so it would be logistically easier/better if we could
> queue this up towards upstream via tip/fastboot.
Yes,
Acked-by: NeilBrown <neilb@suse.de>
I'm not a big fan of autodetect in any case, and this patch seems to
cover all the bases I can think of.
Thanks,
NeilBrown
next prev parent reply other threads:[~2008-09-23 3:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-21 22:45 [PATCH] raid: make RAID autodetect default a KConfig option Arjan van de Ven
2008-09-22 8:27 ` Ingo Molnar
2008-09-23 3:45 ` Neil Brown [this message]
2008-09-23 3:58 ` Arjan van de Ven
2008-09-23 9:15 ` Ingo Molnar
-- strict thread matches above, loose matches on Subject: below --
2008-09-23 15:37 Alan Jenkins
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=18648.26191.479291.883160@notabene.brown \
--to=neilb@suse.de \
--cc=arjan@infradead.org \
--cc=davej@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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