From: Arjan van de Ven <arjan@linux.intel.com>
To: 吴章金 <falcon@meizu.com>, "Greg KH" <gregkh@linuxfoundation.org>
Cc: Dmitry Torokhov <dmitry.torokhov@gmail.com>,
"Luis R. Rodriguez" <mcgrof@do-not-panic.com>,
"tiwai@suse.de" <tiwai@suse.de>, "tj@kernel.org" <tj@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"oleg@redhat.com" <oleg@redhat.com>,
"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
"penguin-kernel@i-love.sakura.ne.jp"
<penguin-kernel@i-love.sakura.ne.jp>,
"joseph.salisbury@canonical.com" <joseph.salisbury@canonical.com>,
"bpoirier@suse.de" <bpoirier@suse.de>,
"Luis R. Rodriguez" <mcgrof@suse.com>
Subject: Re: [RFC v1 0/3] driver-core: add asynch module loading support
Date: Sun, 31 Aug 2014 15:32:19 -0700 [thread overview]
Message-ID: <5403A273.4070504@linux.intel.com> (raw)
In-Reply-To: <99jhsb6abtsilpt3j5nu991b.1409513632114@email.android.com>
On 8/31/2014 1:06 PM, 吴章金 wrote:
> Hi, folks
>
> I'm back to this discussion,
>
> The original requirement of my first RFC patchset is mainly for Android Smartphone use case:
>
> 1. We want light on LCD and draw a logo immediately after power key press(don't consider uboot or lk biotloader here).
> 2. We want the whole kernel boot fast to give user the Android Launch deaktop
> 3. The modem initialization/reset is slow
> 4. The Touchpad firmware upgrade is slow
> 5. We have many cpu cores(up to 8 in latest exynos 5430 and MT6595...)
> 6. We have few schedulable/parallellizable threads
> 7. We compiled all of the modules in the kernel(stupid? avoid modprobe...but lose parallelization in userspace)
>
> So, I think about is that possible to async most of the probes, but still reserve the requred dependencies to let them still work as expected.
you can boot a whole kernel including all graphics in less than 0.5 seconds, even without this patchset.
next parent reply other threads:[~2014-08-31 22:32 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <99jhsb6abtsilpt3j5nu991b.1409513632114@email.android.com>
2014-08-31 22:32 ` Arjan van de Ven [this message]
2014-08-31 22:45 ` [RFC v1 0/3] driver-core: add asynch module loading support Dmitry Torokhov
2014-08-31 22:48 ` Arjan van de Ven
2014-08-31 9:03 Luis R. Rodriguez
2014-08-31 10:13 ` Tejun Heo
2014-08-31 11:02 ` Tejun Heo
2014-08-31 11:05 ` Tejun Heo
2014-08-31 17:52 ` Dmitry Torokhov
2014-08-31 19:26 ` Arjan van de Ven
2014-08-31 20:11 ` Dmitry Torokhov
2014-08-31 11:25 ` David Herrmann
2014-08-31 11:38 ` Tejun Heo
2014-08-31 18:28 ` Dmitry Torokhov
2014-08-31 22:02 ` Tejun Heo
2014-08-31 23:06 ` Dmitry Torokhov
2014-08-31 23:40 ` Tejun Heo
2014-08-31 14:44 ` Arjan van de Ven
2014-08-31 17:50 ` Dmitry Torokhov
2014-08-31 19:24 ` Arjan van de Ven
2014-08-31 19:31 ` Greg KH
2014-08-31 20:14 ` Dmitry Torokhov
2014-08-31 20:40 ` Greg KH
2014-08-31 21:53 ` Tejun Heo
2014-08-31 22:15 ` Greg KH
2014-08-31 22:53 ` Tejun Heo
2014-08-31 23:20 ` Arjan van de Ven
2014-08-31 23:29 ` Tejun Heo
2014-08-31 22:51 ` Dmitry Torokhov
2014-08-31 23:03 ` Tejun Heo
2014-09-04 21:21 ` Luis R. Rodriguez
2014-09-04 21:52 ` Greg KH
2014-08-31 16:41 ` Greg KH
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=5403A273.4070504@linux.intel.com \
--to=arjan@linux.intel.com \
--cc=akpm@linux-foundation.org \
--cc=bpoirier@suse.de \
--cc=dmitry.torokhov@gmail.com \
--cc=falcon@meizu.com \
--cc=gregkh@linuxfoundation.org \
--cc=joseph.salisbury@canonical.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mcgrof@do-not-panic.com \
--cc=mcgrof@suse.com \
--cc=oleg@redhat.com \
--cc=penguin-kernel@i-love.sakura.ne.jp \
--cc=tiwai@suse.de \
--cc=tj@kernel.org \
/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.