DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition;
        b=LeT3rdUB5K5XOj8yWepla+mdCtGEMixzess8iMiBIS1fDMAXdJ4zHk69FzM1NtWGffwGh0quagmBB95rFx7BCbEw1C6piSd0M/nX21pom0zsg0+TQKxXMBs99ZdtzJAO+AD8p83YjR4dtQACX0vem5YoUrikwT1vGgb9UsMmP/8=
Message-ID: <4ae3c140510261006q193e466bjc90ace3e7979393c@mail.gmail.com>
Date: Wed, 26 Oct 2005 13:06:16 -0400
From: Xin Zhao <uszhaoxin@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: can someone explain how to implement callback in kernel?
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7BIT
Content-Disposition: inline
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 756
Lines: 21

I am writing a device driver. I want to achieve asynchronous I/O. What
I want to do is as follows:

1. the driver issues a request to the device. Instead of waiting , it
schedules a callback,  then return.

2. after the device serves the request, the callback should be
triggered to finish the rest of work for this request.

This seems to be a standard callback working flow. But I don't know
how to implement this. Can someone give me a brief idea or point me to
some link about this?

Thanks in advance!

Xin
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/