relay_open(9) [centos man page]

RELAY_OPEN(9)						      relay interface support						     RELAY_OPEN(9)

NAME

       relay_open - create a new relay channel

SYNOPSIS

       struct rchan * relay_open(const char * base_filename, struct dentry * parent, size_t subbuf_size, size_t n_subbufs,
				 struct rchan_callbacks * cb, void * private_data);

ARGUMENTS

       base_filename
	   base name of files to create, NULL for buffering only

       parent
	   dentry of parent directory, NULL for root directory or buffer

       subbuf_size
	   size of sub-buffers

       n_subbufs
	   number of sub-buffers

       cb
	   client callback functions

       private_data
	   user-defined data

DESCRIPTION

       Returns channel pointer if successful, NULL otherwise.

       Creates a channel buffer for each cpu using the sizes and attributes specified. The created channel buffer files will be named
       base_filename0...base_filenameN-1. File permissions will be S_IRUSR.

COPYRIGHT

Kernel Hackers Manual 3.10					     June 2014							     RELAY_OPEN(9)

DEBUGFS_CREATE_FILE(9)					      The debugfs filesystem					    DEBUGFS_CREATE_FILE(9)

NAME

       debugfs_create_file - create a file in the debugfs filesystem

SYNOPSIS

       struct dentry * debugfs_create_file(const char * name, umode_t mode, struct dentry * parent, void * data,
					   const struct file_operations * fops);

ARGUMENTS

       name
	   a pointer to a string containing the name of the file to create.

       mode
	   the permission that the file should have.

       parent
	   a pointer to the parent dentry for this file. This should be a directory dentry if set. If this paramater is NULL, then the file will
	   be created in the root of the debugfs filesystem.

       data
	   a pointer to something that the caller will want to get to later on. The inode.i_private pointer will point to this value on the open
	   call.

       fops
	   a pointer to a struct file_operations that should be used for this file.

DESCRIPTION

       This is the basic "create a file" function for debugfs. It allows for a wide range of flexibility in creating a file, or a directory (if
       you want to create a directory, the debugfs_create_dir function is recommended to be used instead.)

       This function will return a pointer to a dentry if it succeeds. This pointer must be passed to the debugfs_remove function when the file is
       to be removed (no automatic cleanup happens if your module is unloaded, you are responsible here.) If an error occurs, NULL will be
       returned.

       If debugfs is not enabled in the kernel, the value -ENODEV will be returned.

COPYRIGHT

Kernel Hackers Manual 3.10					     June 2014						    DEBUGFS_CREATE_FILE(9)