xdr_init_encode(9) [centos man page]

XDR_INIT_ENCODE(9)						 Linux Networking						XDR_INIT_ENCODE(9)

NAME

       xdr_init_encode - Initialize a struct xdr_stream for sending data.

SYNOPSIS

       void xdr_init_encode(struct xdr_stream * xdr, struct xdr_buf * buf, __be32 * p);

ARGUMENTS

       xdr
	   pointer to xdr_stream struct

       buf
	   pointer to XDR buffer in which to encode data

       p
	   current pointer inside XDR buffer

NOTE

       at the moment the RPC client only passes the length of our scratch buffer in the xdr_buf's header kvec. Previously this meant we needed to
       call xdr_adjust_iovec after encoding the data. With the new scheme, the xdr_stream manages the details of the buffer length, and takes care
       of adjusting the kvec length for us.

COPYRIGHT

Kernel Hackers Manual 3.10					     June 2014							XDR_INIT_ENCODE(9)

rpc_xdr(3)						     Library Functions Manual							rpc_xdr(3)

NAME

       rpc_xdr,  xdr_accepted_reply, xdr_authunix_parms, xdr_callhdr, xdr_callmsg, xdr_opaque_auth, xdr_rejected_reply, xdr_replymsg - XDR library
       routines for ONC remote procedure calls

SYNOPSIS

       #include <rpc/xdr.h>

       xdr_accepted_reply(	XDR *xdrs,	struct accepted_reply *ar);

       xdr_authunix_parms(	XDR *xdrs,	struct authunix_parms *aupp);

       void xdr_callhdr(      XDR *xdrs,      struct rpc_msg *chdr);

       xdr_callmsg(	 XDR *xdrs,	 struct rpc_msg *cmsg);

       xdr_opaque_auth(      XDR *xdrs,      struct opaque_auth *ap);

       xdr_rejected_reply(	XDR *xdrs,	struct rejected_reply *rr);

       xdr_replymsg(	  XDR *xdrs,	  struct rpc_msg *rmsg);

DESCRIPTION

       These routines allow C programs to make procedure calls on other machines across the network.  First, the client calls a procedure to  send
       a  data	packet	to the server.	Upon receipt of the packet, the server calls a dispatch routine to perform the requested service, and then
       sends back a reply.  Finally, the procedure call returns to the client.

       Unless otherwise indicated, the routines described in this reference page are thread safe (that is, they can be used  safely  in  a  multi-
       threaded  environment).	 Routines  that  are not thread safe are flagged as such.  Encodes RPC reply messages.	This routine is useful for
       users who wish to generate RPC-style messages without using the RPC package.  Describes UNIX credentials.  This routine is useful for users
       who  wish to generate these credentials without using the RPC authentication package.  Describes RPC call header messages.  This routine is
       useful for users who wish to generate RPC-style messages without using the RPC package.	Describes RPC call messages.  This routine is use-
       ful  for  users	who wish to generate RPC-style messages without using the RPC package.	Describes RPC authentication information messages.
       This routine is useful for users who wish to generate RPC-style messages without using the RPC  package.   Describes  RPC  reply  messages.
       This  routine  is  useful  for  users who want to generate RPC-style messages without using the RPC package.  Describes RPC reply messages.
       This routine is useful for users who want to generate RPC-style messages without using the RPC package.

RELATED INFORMATION

       rpc_clnt(3), rpc_misc(3), rpc_svc(3), xdr(3)

       Remote Procedure Calls: Protocol Specifications - RFC 1050 delim off

																	rpc_xdr(3)