From: Paul Mundt <lethal@linux-sh.org>
To: Bjo Breiskoll <bjo@nefkom.net>
Cc: "Linux-Kernel@Vger. Kernel. Org" <linux-kernel@vger.kernel.org>
Subject: Re: Relay Subsystem the 2nd.
Date: Wed, 23 Aug 2006 09:57:36 +0900 [thread overview]
Message-ID: <20060823005736.GA8047@localhost.hsdv.com> (raw)
In-Reply-To: <002d01c6c645$9be1afe0$03b2a8c0@bjoserver>
On Wed, Aug 23, 2006 at 01:49:29AM +0200, Bjo Breiskoll wrote:
> back to my question last week. I would like to implement a new kernel-modul
> with the ability to write data from kernelspace to userspace via the new
> relay subsystem. The less info from block/blktrace.c is insufficient
> unfortunately. The userspace-program should be able to "listen" to the
> kernel-modul if there is new data written. My first Implementation with data
> exchange over copy_to_user() and a char-device is insufficient. So i need an
> hint for something like blocked-IO for relay-files. Is this possible with
> the new relay-subsystem?
>
Is there something insufficient with poll() on relay files?
next prev parent reply other threads:[~2006-08-23 0:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-22 23:49 Relay Subsystem the 2nd Bjo Breiskoll
2006-08-23 0:57 ` Paul Mundt [this message]
2006-08-26 8:28 ` AW: " Bjo Breiskoll
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=20060823005736.GA8047@localhost.hsdv.com \
--to=lethal@linux-sh.org \
--cc=bjo@nefkom.net \
--cc=linux-kernel@vger.kernel.org \
/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