From: Daniel Borkmann <llug.dan@googlemail.com>
To: "Bartłomiej Zimoń" <uzi18@o2.pl>
Cc: linux-kernel@vger.kernel.org
Subject: Re: userspace notification from module
Date: Sat, 02 Jan 2010 13:36:55 +0100 [thread overview]
Message-ID: <4B3F3DE7.7030809@googlemail.com> (raw)
In-Reply-To: <4b387f18.307edfdc.4b3f399c.3bc2e@o2.pl>
Hi Bartłomiej,
Bartłomiej Zimoń wrote:
> Use inotify from userspace could be interesting for such data,
> but looks like sysfs/procfs doesn't send signal about data changed in file or maybe i'm wrong?
>
> If sysfs/procfs is wrong for that so must create device file, but here secound problem
> how to notify that file/buffer has new data?
Actually, the file content of a procfs file is volatile and generated on
the fly, just have a look at some device drivers or at the API.
Did you have a look at the netlink protocol for communication from
kernel to userspace?
Cheers,
Daniel
next prev parent reply other threads:[~2010-01-02 12:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-02 12:18 userspace notification from module Bartłomiej Zimoń
2010-01-02 12:36 ` Daniel Borkmann [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-01-02 13:29 Bartłomiej Zimoń
2010-01-02 14:04 ` Daniel Borkmann
2010-01-02 12:02 Bartłomiej Zimoń
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=4B3F3DE7.7030809@googlemail.com \
--to=llug.dan@googlemail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=uzi18@o2.pl \
/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