From: "Richard B. Johnson" <root@chaos.analogic.com>
To: "Ihar 'Philips' Filipau" <filia@softhome.net>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Pankaj Garg <PGarg@MEGISTO.com>,
Zwane Mwaikambo <zwane@linuxpower.ca>
Subject: Re: Messaging between kernel modules and User Apps
Date: Thu, 21 Aug 2003 13:23:06 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.53.0308211318500.3389@chaos> (raw)
In-Reply-To: <3F44F9D0.5010606@softhome.net>
On Thu, 21 Aug 2003, Ihar 'Philips' Filipau wrote:
> Zwane Mwaikambo wrote:
> >>The de facto standard for network devices is to use sockets.
> >>For character and and block devices Unix/Linux uses the
> >>open/poll/ioctl/read mechanisms.
> >
> > That sounds fine, but..
> >
> >>You could send your module a pid via proc and have it send a
> >>signal to your application as a result of an event.
> >
> > ... please don't even entertain such sick ideas.
>
> Especially when there is fcntl(F_{G,S}ET{OWN,SIG}) infrastructure in
> place - kill_fasync().
>
Just getting 'even' for the last time I advised poll()/ioctl() and
I was pummeled with "No... use /proc"! Of course the "best" method
is to open a file in the kernel module and have the user poll for
a change in length ->;^;<-)
Cheers,
Dick Johnson
Penguin : Linux version 2.4.20 on an i686 machine (797.90 BogoMips).
Note 96.31% of all statistics are fiction.
next prev parent reply other threads:[~2003-08-21 17:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mYVo.39N.19@gated-at.bofh.it>
[not found] ` <mZou.3Ff.29@gated-at.bofh.it>
[not found] ` <n0ud.4F4.15@gated-at.bofh.it>
2003-08-21 16:56 ` Ihar 'Philips' Filipau
2003-08-21 17:23 ` Richard B. Johnson [this message]
2003-08-21 15:05 Heater, Daniel (IndSys, GEFanuc, VMIC)
-- strict thread matches above, loose matches on Subject: below --
2003-08-21 14:44 Pankaj Garg
2003-08-21 14:53 ` P
2003-08-21 15:14 ` Richard B. Johnson
2003-08-21 15:59 ` Zwane Mwaikambo
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=Pine.LNX.4.53.0308211318500.3389@chaos \
--to=root@chaos.analogic.com \
--cc=PGarg@MEGISTO.com \
--cc=filia@softhome.net \
--cc=linux-kernel@vger.kernel.org \
--cc=zwane@linuxpower.ca \
/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
all inboxes | Powered by JetHome®