From: Lee Revell <rlrevell@joe-job.com>
To: Ravindra Nadgauda <rnadgauda@velankani.com>
Cc: "'Linux Kernel Mailing List'" <linux-kernel@vger.kernel.org>
Subject: Re: Signals/ Communication from kernel to user!
Date: Mon, 28 Feb 2005 16:17:45 -0500 [thread overview]
Message-ID: <1109625466.9273.24.camel@mindpipe> (raw)
In-Reply-To: <042701c51dab$561ef650$280e000a@blr.velankani.com>
On Mon, 2005-02-28 at 21:06 +0530, Ravindra Nadgauda wrote:
>
> Hello,
> We wanted to establish a communication from kernel module (possibly a
> driver) to a user level process.
>
> Wanted to know whether signals can be used for this purpose OR there any
> other (better) methods of communication??
If you need fast IPC forget about signals. They are way too slow.
The traditional UNIX way for userspace to talk to the kernel has been
ioctls. For various reasons ioctls are not highly regarded in the Linux
kernel community.
I believe the currently favored method is to have the driver create
sysfs entries which userspace read()s and write()s.
Really, your question is too vague. It would help if you said what
exactly you are trying to accomplish.
Lee
next prev parent reply other threads:[~2005-02-28 21:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.hgi75u0.1cnmhaa@ifi.uio.no>
2005-02-28 15:23 ` swapper: page allocation failure. order:1, mode:0x20 Benjamin L. Shi
2005-02-28 15:36 ` Signals/ Communication from kernel to user! Ravindra Nadgauda
2005-02-28 16:48 ` Timothy R. Chavez
2005-02-28 19:13 ` Der Herr Hofrat
2005-02-28 21:17 ` Lee Revell [this message]
2005-02-28 15:38 ` swapper: page allocation failure. order:1, mode:0x20 Bernd Schubert
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=1109625466.9273.24.camel@mindpipe \
--to=rlrevell@joe-job.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rnadgauda@velankani.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