From: Andrew Morton <akpm@linux-foundation.org>
To: Arjan van de Ven <arjan@infradead.org>
Cc: linux-kernel@vger.kernel.org, torvalds@linux-foundation.org,
mingo@elte.hu, linux-ide@vger.kernel.org,
linux-scsi@vger.kernel.org, linux-acpi@vger.kernel.org
Subject: Re: [PATCH 1/6] fastboot: Asynchronous function calls to speed up kernel boot
Date: Mon, 5 Jan 2009 20:25:14 -0800 [thread overview]
Message-ID: <20090105202514.399da36e.akpm@linux-foundation.org> (raw)
In-Reply-To: <20090105201041.3289d3dd@infradead.org>
On Mon, 5 Jan 2009 20:10:41 -0800 Arjan van de Ven <arjan@infradead.org> wrote:
> kernel/async.c | 307 ++++++++++++++++++++++++++++++++++++++++++++++++
Am still wondering if this is unacceptably duplicative of dhowells's
slow-work infrastructure: http://lkml.org/lkml/2008/11/20/193
next prev parent reply other threads:[~2009-01-06 4:25 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20090105200959.04a626ac@infradead.org>
2009-01-06 4:10 ` [PATCH 1/6] fastboot: Asynchronous function calls to speed up kernel boot Arjan van de Ven
2009-01-06 4:25 ` Andrew Morton [this message]
2009-01-06 4:37 ` Arjan van de Ven
2009-01-06 13:57 ` Arjan van de Ven
2009-01-14 5:32 ` Zhang Rui
2009-01-14 9:04 ` Arjan van de Ven
2009-01-15 5:55 ` Zhang Rui
2009-01-06 4:11 ` [PATCH 2/6] fastboot: make scsi probes asynchronous Arjan van de Ven
2009-01-09 18:17 ` Mark Lord
2009-01-06 4:12 ` [PATCH 3/6] fastboot: make the libata port scan asynchronous Arjan van de Ven
2009-01-07 9:12 ` Bert Wesarg
2009-01-06 4:12 ` [PATCH 4/6] fastboot: make ACPI bus drivers probe asynchronous Arjan van de Ven
2009-01-07 14:12 ` Yong Wang
2009-01-07 17:25 ` Arjan van de Ven
2009-01-06 4:13 ` [PATCH 5/6] bootchart: improve output Arjan van de Ven
2009-01-06 4:13 ` [PATCH 6/6] fastboot: Make libata initialization even more async Arjan van de Ven
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=20090105202514.399da36e.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=arjan@infradead.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=torvalds@linux-foundation.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 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).