From: tom.leiming@gmail.com
To: arjan@infradead.org
Cc: linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
cornelia.huck@de.ibm.com, Ming Lei <tom.leiming@gmail.com>
Subject: [PATCH 1/2] kernel:async function call:introduce async_run_inatomic(v3)
Date: Sat, 16 May 2009 21:54:17 +0800 [thread overview]
Message-ID: <1242482058-5203-1-git-send-email-tom.leiming@gmail.com> (raw)
From: Ming Lei <tom.leiming@gmail.com>
The purpose of this function is to offer a simple way to schedule an
asynchronous thread from an atomic context, because there are not any
functions which can create and start a kernel thread in atomic contexts.
Now async_run_inatomic() uses a distinct running list in order to avoid
slowing down synchronization within the general domain.
The comment for async_run_inatomic is under guideline from Cornelia Huck.
Signed-off-by: Ming Lei <tom.leiming@gmail.com>
Signed-off-by: Cornelia Huck <cornelia.huck@de.ibm.com>
---
include/linux/async.h | 2 ++
kernel/async.c | 23 +++++++++++++++++++++++
2 files changed, 25 insertions(+), 0 deletions(-)
diff --git a/include/linux/async.h b/include/linux/async.h
index 18ce92b..9ff62af 100644
--- a/include/linux/async.h
+++ b/include/linux/async.h
@@ -16,6 +16,8 @@
typedef u64 async_cookie_t;
typedef void (async_func_ptr) (void *data, async_cookie_t cookie);
+extern int async_run_inatomic(async_func_ptr *ptr, void *data);
+
extern async_cookie_t async_schedule(async_func_ptr *ptr, void *data);
extern async_cookie_t async_schedule_domain(async_func_ptr *ptr, void *data,
struct list_head *list);
diff --git a/kernel/async.c b/kernel/async.c
index 8663f5b..adc0455 100644
--- a/kernel/async.c
+++ b/kernel/async.c
@@ -65,6 +65,7 @@ static async_cookie_t next_cookie = 1;
static LIST_HEAD(async_pending);
static LIST_HEAD(async_running);
+static LIST_HEAD(async_running_no_sync);
static DEFINE_SPINLOCK(async_lock);
static int async_enabled = 0;
@@ -222,6 +223,28 @@ static async_cookie_t __async_schedule(async_func_ptr *ptr, void *data,
return newcookie;
}
+ /**
+ * async_run_inatomic - in atomic contexts schedule a function for
+ * asynchronous execution
+ *
+ * @ptr: function to execute asynchronously
+ * @data: data pointer to pass to the function
+ *
+ * The purpose of this function is to offer a simple way to schedule an
+ * asynchronous thread from an atomic context.
+ *
+ * Return zero one success, !zero on failured
+ * Note: async_run_inatomic() uses a distinct running list in order
+ * to avoid slowing down synchronization within the general domain.
+ * Since it does not return a cookie for checkpointing, it is for callers
+ * that don't need later synchronization.
+ */
+int async_run_inatomic(async_func_ptr *ptr, void *data)
+{
+ return !__async_schedule(ptr, data, &async_running_no_sync, 1);
+}
+EXPORT_SYMBOL_GPL(async_run_inatomic);
+
/**
* async_schedule - schedule a function for asynchronous execution
* @ptr: function to execute asynchronously
--
1.6.0.GIT
next reply other threads:[~2009-05-16 13:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-16 13:54 tom.leiming [this message]
2009-05-16 13:54 ` [PATCH 2/2] driver core:firmware:fix request_firmware_nowait tom.leiming
2009-05-18 11:15 ` Cornelia Huck
2009-05-18 11:10 ` [PATCH 1/2] kernel:async function call:introduce async_run_inatomic(v3) Cornelia Huck
2009-05-18 13:58 ` 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=1242482058-5203-1-git-send-email-tom.leiming@gmail.com \
--to=tom.leiming@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=arjan@infradead.org \
--cc=cornelia.huck@de.ibm.com \
--cc=linux-kernel@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox