From: "Bart Van Assche" <bart.vanassche@gmail.com>
To: "Jinkai Gao" <mickeygjk@gmail.com>
Cc: linux-kernel@vger.kernel.org, "Arjan van de Ven" <arjan@infradead.org>
Subject: Re: Suggestion: LKM should be able to add system call for itself
Date: Mon, 7 Jul 2008 10:40:27 +0200 [thread overview]
Message-ID: <e2e108260807070140l3f8eaf06w7ee7e8a4ae42f2c2@mail.gmail.com> (raw)
In-Reply-To: <fb82a8210807062209t6cfe3e46m50a11b577f0540e7@mail.gmail.com>
On Mon, Jul 7, 2008 at 7:09 AM, Jinkai Gao <mickeygjk@gmail.com> wrote:
> LKM(loadable kernel module) was first introduced for drivers. Users
> rarely need to talk to the modules directly. If does, several methods
> are available now, such as /proc file, interruption, etc. However,
> these interfaces are predefined, which makes the communication between
> user space and kernel space quite restricted.
Did you already have a look at e.g. http://lwn.net/Kernel/LDD3/ for
suggestions of alternatives for communication between userspace and
kernel modules ? Alternatives to system calls are e.g. ioctl's, memory
mapped I/O and sockets. The last alternative is used by udevd
(PF_NETLINK).
Bart.
next prev parent reply other threads:[~2008-07-07 8:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-07 5:09 Jinkai Gao
2008-07-07 7:01 ` Arjan van de Ven
2008-07-07 12:12 ` Jinkai Gao
2008-07-07 14:29 ` Arjan van de Ven
2008-07-07 8:40 ` Bart Van Assche [this message]
2008-07-07 12:36 ` Jinkai Gao
2008-07-07 14:16 ` Bart Van Assche
2008-07-07 14:42 ` Jan Engelhardt
2008-07-07 9:35 ` Jan Engelhardt
2008-07-07 14:00 ` Jinkai Gao
2008-07-07 14:16 ` Josh Boyer
2008-07-07 16:33 ` Eduard - Gabriel Munteanu
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=e2e108260807070140l3f8eaf06w7ee7e8a4ae42f2c2@mail.gmail.com \
--to=bart.vanassche@gmail.com \
--cc=arjan@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mickeygjk@gmail.com \
/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
Powered by JetHome