'\" t
.\"     Title: rpc_mkpipe_dentry
.\"    Author: [FIXME: author] [see http://docbook.sf.net/el/author]
.\" Generator: DocBook XSL Stylesheets v1.79.1 <http://docbook.sf.net/>
.\"      Date: January 2017
.\"    Manual: Linux Networking
.\"    Source: Kernel Hackers Manual 4.8.15
.\"  Language: English
.\"
.TH "RPC_MKPIPE_DENTRY" "9" "January 2017" "Kernel Hackers Manual 4\&.8\&." "Linux Networking"
.\" -----------------------------------------------------------------
.\" * Define some portability stuff
.\" -----------------------------------------------------------------
.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
.\" http://bugs.debian.org/507673
.\" http://lists.gnu.org/archive/html/groff/2009-02/msg00013.html
.\" ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
.ie \n(.g .ds Aq \(aq
.el       .ds Aq '
.\" -----------------------------------------------------------------
.\" * set default formatting
.\" -----------------------------------------------------------------
.\" disable hyphenation
.nh
.\" disable justification (adjust text to left margin only)
.ad l
.\" -----------------------------------------------------------------
.\" * MAIN CONTENT STARTS HERE *
.\" -----------------------------------------------------------------
.SH "NAME"
rpc_mkpipe_dentry \- make an rpc_pipefs file for kernel<\->userspace communication
.SH "SYNOPSIS"
.HP \w'struct\ dentry\ *\ rpc_mkpipe_dentry('u
.BI "struct dentry * rpc_mkpipe_dentry(struct\ dentry\ *\ " "parent" ", const\ char\ *\ " "name" ", void\ *\ " "private" ", struct\ rpc_pipe\ *\ " "pipe" ");"
.SH "ARGUMENTS"
.PP
\fIparent\fR
.RS 4
dentry of directory to create new
\(lqpipe\(rq
in
.RE
.PP
\fIname\fR
.RS 4
name of pipe
.RE
.PP
\fIprivate\fR
.RS 4
private data to associate with the pipe, for the caller\*(Aqs use
.RE
.PP
\fIpipe\fR
.RS 4
rpc_pipe
containing input parameters
.RE
.SH "DESCRIPTION"
.PP
Data is made available for userspace to read by calls to
\fBrpc_queue_upcall\fR\&. The actual reads will result in calls to
\fIops\fR\->upcall, which will be called with the file pointer, message, and userspace buffer to copy to\&.
.PP
Writes can come at any time, and do not necessarily have to be responses to upcalls\&. They will result in calls to
\fImsg\fR\->downcall\&.
.PP
The
\fIprivate\fR
argument passed here will be available to all these methods from the file pointer, via RPC_I(file_inode(file))\->private\&.
.SH "COPYRIGHT"
.br