1<html><head><meta http-equiv="Content-Type" content="text/html; charset=ANSI_X3.4-1968"><title>rpc_mkpipe_dentry</title><meta name="generator" content="DocBook XSL Stylesheets V1.78.1"><link rel="home" href="index.html" title="Linux Networking and Network Devices APIs"><link rel="up" href="ch01s05.html" title="SUN RPC subsystem"><link rel="prev" href="API-rpc-queue-upcall.html" title="rpc_queue_upcall"><link rel="next" href="API-rpc-unlink.html" title="rpc_unlink"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center"><span class="phrase">rpc_mkpipe_dentry</span></th></tr><tr><td width="20%" align="left"><a accesskey="p" href="API-rpc-queue-upcall.html">Prev</a> </td><th width="60%" align="center">SUN RPC subsystem</th><td width="20%" align="right"> <a accesskey="n" href="API-rpc-unlink.html">Next</a></td></tr></table><hr></div><div class="refentry"><a name="API-rpc-mkpipe-dentry"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>rpc_mkpipe_dentry — 2 make an rpc_pipefs file for kernel<->userspace communication 3 </p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class="funcsynopsis"><table border="0" class="funcprototype-table" summary="Function synopsis" style="cellspacing: 0; cellpadding: 0;"><tr><td><code class="funcdef">struct dentry * <b class="fsfunc">rpc_mkpipe_dentry </b>(</code></td><td>struct dentry * <var class="pdparam">parent</var>, </td></tr><tr><td> </td><td>const char * <var class="pdparam">name</var>, </td></tr><tr><td> </td><td>void * <var class="pdparam">private</var>, </td></tr><tr><td> </td><td>struct rpc_pipe * <var class="pdparam">pipe</var><code>)</code>;</td></tr></table><div class="funcprototype-spacer"> </div></div></div><div class="refsect1"><a name="idp1097318820"></a><h2>Arguments</h2><div class="variablelist"><dl class="variablelist"><dt><span class="term"><em class="parameter"><code>parent</code></em></span></dt><dd><p> 4 dentry of directory to create new <span class="quote">“<span class="quote">pipe</span>”</span> in 5 </p></dd><dt><span class="term"><em class="parameter"><code>name</code></em></span></dt><dd><p> 6 name of pipe 7 </p></dd><dt><span class="term"><em class="parameter"><code>private</code></em></span></dt><dd><p> 8 private data to associate with the pipe, for the caller's use 9 </p></dd><dt><span class="term"><em class="parameter"><code>pipe</code></em></span></dt><dd><p> 10 <span class="structname">rpc_pipe</span> containing input parameters 11 </p></dd></dl></div></div><div class="refsect1"><a name="idp1097323980"></a><h2>Description</h2><p> 12 Data is made available for userspace to read by calls to 13 <code class="function">rpc_queue_upcall</code>. The actual reads will result in calls to 14 <em class="parameter"><code>ops</code></em>->upcall, which will be called with the file pointer, 15 message, and userspace buffer to copy to. 16 </p><p> 17 18 Writes can come at any time, and do not necessarily have to be 19 responses to upcalls. They will result in calls to <em class="parameter"><code>msg</code></em>->downcall. 20 </p><p> 21 22 The <em class="parameter"><code>private</code></em> argument passed here will be available to all these methods 23 from the file pointer, via RPC_I(file_inode(file))->private. 24</p></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="API-rpc-queue-upcall.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="ch01s05.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="API-rpc-unlink.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top"><span class="phrase">rpc_queue_upcall</span> </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> <span class="phrase">rpc_unlink</span></td></tr></table></div></body></html> 25