From: hpa@zytor.com (H. Peter Anvin)
To: linux-kernel@vger.kernel.org
Subject: Re: upcalls from kernel code to user space daemons
Date: Fri, 18 Jun 2004 23:08:29 +0000 (UTC) [thread overview]
Message-ID: <cavsld$bem$1@terminus.zytor.com> (raw)
In-Reply-To: 1087236468.10367.27.camel@stevef95.austin.ibm.com
Followup to: <1087236468.10367.27.camel@stevef95.austin.ibm.com>
By author: Steve French <smfltc@us.ibm.com>
In newsgroup: linux.dev.kernel
>
> Is there a good terse example of an upcall from a kernel module (such as
> filesystem) to an optional user space helper daemon? The NFS RPC
> example seems more complicated than what I would like as does the
> captive ioctl approach which I see in a few places.
>
autofs does this by having the kernel write to the write-end of a
pipe, and have the userspace daemon read from the read end of the same
pipe.
The same thing can be done with sockets.
-hpa
prev parent reply other threads:[~2004-06-18 23:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-14 18:07 upcalls from kernel code to user space daemons Steve French
2004-06-14 18:30 ` Chris Friesen
2004-06-14 21:40 ` Oliver Neukum
2004-06-14 21:57 ` Chris Friesen
2004-06-14 22:08 ` Bernd Petrovitsch
2004-06-14 22:22 ` Chris Friesen
2004-06-14 22:54 ` Tim Hockin
2004-06-14 23:10 ` Randy.Dunlap
2004-06-14 22:54 ` Steve French
2004-06-15 9:06 ` Oliver Neukum
2004-06-18 23:08 ` H. Peter Anvin [this message]
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='cavsld$bem$1@terminus.zytor.com' \
--to=hpa@zytor.com \
--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