Lines Matching refs:relay

4 relay interface (formerly relayfs)
7 The relay interface provides a means for kernel applications to
9 to userspace via user-defined 'relay channels'.
11 A 'relay channel' is a kernel->user data relay mechanism implemented
13 represented as a regular file ('relay file') in user space.  Kernel
16 buffer.  User space applications mmap() or read() from the relay files
17 and retrieve the data as it becomes available.  The relay files
22 up to the kernel client; the relay interface does however provide
24 buffer data.  The relay interface doesn't implement any form of data
28 This document provides an overview of the relay interface API.  The
30 functions in the relay interface code - please see that for details.
35 Each relay channel has one buffer per CPU, each buffer has one or more
50 A relay channel can operate in a mode where it will overwrite data not
53 The relay channel itself does not provide for communication of such
64 One of the major goals of the relay interface is to provide a low
70 klog and relay-apps example code
73 The relay interface itself is ready to use, but to make things easier,
76 The relay-apps example tarball, available on the relay sourceforge
79 kernel sides of a relay application.  When combined these two sets of
83 The 'klog debugging functions' patch (klog.patch in the relay-apps
87 whether the relay interface is compiled into the kernel or not.  These
93 It is of course possible to use the relay interface from scratch,
94 i.e. without using any of the relay-apps example code or klog, but
104 klog and the relay-apps examples can be found in the relay-apps
107 The relay interface user space API
110 The relay interface implements basic file operations for user space
111 access to relay channel buffer data.  Here are the file operations
145 In order for a user application to make use of relay files, the
158 The relay interface kernel API
161 Here's a summary of the API the relay interface provides to in-kernel clients:
205 want a directory structure to contain your relay files, you should
228     * create_buf_file() callback.  Creates relay file in debugfs.
241     * remove_buf_file() callback.  Removes relay file from debugfs.
251     * relay interface callbacks
296 writes in a spinlock, or by copying a write function from relay.h and
317 relay channels can be used in either of two modes - 'overwrite' or
335 As explained above, a relay channel is made of up one or more
371 to make sense, the consumer is responsible for notifying the relay
445 a separate array.  See the 'reserve' example in the relay-apps tarball
483 For news, example code, mailing list, etc. see the relay interface homepage:
491 The ideas and specs for the relay interface came about as a result of