Lines Matching refs:relay

1 relay interface (formerly relayfs)
4 The relay interface provides a means for kernel applications to
6 to userspace via user-defined 'relay channels'.
8 A 'relay channel' is a kernel->user data relay mechanism implemented
10 represented as a regular file ('relay file') in user space.  Kernel
13 buffer.  User space applications mmap() or read() from the relay files
14 and retrieve the data as it becomes available.  The relay files
19 up to the kernel client; the relay interface does however provide
21 buffer data.  The relay interface doesn't implement any form of data
25 This document provides an overview of the relay interface API.  The
27 functions in the relay interface code - please see that for details.
32 Each relay channel has one buffer per CPU, each buffer has one or more
47 A relay channel can operate in a mode where it will overwrite data not
50 The relay channel itself does not provide for communication of such
61 One of the major goals of the relay interface is to provide a low
67 klog and relay-apps example code
70 The relay interface itself is ready to use, but to make things easier,
73 The relay-apps example tarball, available on the relay sourceforge
76 kernel sides of a relay application.  When combined these two sets of
80 The 'klog debugging functions' patch (klog.patch in the relay-apps
84 whether the relay interface is compiled into the kernel or not.  These
90 It is of course possible to use the relay interface from scratch,
91 i.e. without using any of the relay-apps example code or klog, but
101 klog and the relay-apps examples can be found in the relay-apps
104 The relay interface user space API
107 The relay interface implements basic file operations for user space
108 access to relay channel buffer data.  Here are the file operations
140 In order for a user application to make use of relay files, the
151 The relay interface kernel API
154 Here's a summary of the API the relay interface provides to in-kernel clients:
198 want a directory structure to contain your relay files, you should
221  * create_buf_file() callback.  Creates relay file in debugfs.
234  * remove_buf_file() callback.  Removes relay file from debugfs.
244  * relay interface callbacks
289 writes in a spinlock, or by copying a write function from relay.h and
310 relay channels can be used in either of two modes - 'overwrite' or
328 As explained above, a relay channel is made of up one or more
364 to make sense, the consumer is responsible for notifying the relay
438 a separate array.  See the 'reserve' example in the relay-apps tarball
476 For news, example code, mailing list, etc. see the relay interface homepage:
484 The ideas and specs for the relay interface came about as a result of