Lines Matching refs:memory

1 This file documents how to use memory mapped I/O with netlink.
18 user-space memory without copying them as done with regular socket I/O,
22 The TX ring is used to process messages directly from user-space memory, the
29 In order to use memory mapped netlink I/O, user-space needs three main changes:
51 On kernel side, in order to make use of memory mapped I/O on receive, the
52 originating netlink subsystem needs to support memory mapped I/O, otherwise
55 Dumps of kernel databases automatically support memory mapped I/O.
58 use memory from the TX ring instead of (usually) a buffer declared on the
62 Structured and definitions for using memory mapped I/O are contained in
68 Each ring contains a number of continuous memory blocks, containing frames of
83 the ring just contains the frames in a continuous memory zone.
94 Frames are grouped into blocks, where each block is a continuous region of memory
104 - nm_block_size must be a multiple of the architectures memory page size.
116 When the kernel can't allocate physically continuous memory for a ring block,
117 it will fall back to use physically discontinuous memory. This might affect
185 			not support memory mapped I/O. Appropriate action is
271 				/* Regular memory mapped frame */