Lines Matching +full:application +full:- +full:notes
16 4 DMAENGINE DRIVER DEVELOPER NOTES
18 4.2 "My application needs exclusive control of hardware channels"
22 ---
27 bulk memory transfers/transforms with support for inter-transactional
37 xor-parity-calculations of the md-raid5 driver using the offload engines
47 operations to be submitted, like xor->copy->xor in the raid5 case. The
60 memcpy - memory copy between a source and a destination buffer
61 memset - fill a destination buffer with a byte value
62 xor - xor a series of source buffers and write the result to a
64 xor_val - xor a series of source buffers and set a flag if the
67 pq - generate the p+q (raid6 syndrome) from a series of source buffers
68 pq_val - validate that a p and or q buffer are in sync with a given series of
70 datap - (raid6_datap_recov) recover a raid6 data block and the p block
72 2data - (raid6_2data_recov) recover 2 raid6 data blocks from the given
76 The return value is non-NULL and points to a 'descriptor' when the operation
79 operations complete. When an application needs to submit a chain of
82 acknowledged by the application before the offload engine driver is allowed to
94 manage the channel. Once a driver-specific threshold is met the driver
95 automatically issues pending operations. An application can force this
97 channels since the application has no knowledge of channel to operation
101 There are two methods for an application to learn about the completion
108 called in application context if the operation is carried out
110 async_<operation>, or when the application needs to submit a chain of
122 Perform a xor->copy->xor operation where each operation depends on the
150 submit->depend_tx = tx;
167 4 DRIVER DEVELOPMENT NOTES
177 4.2 "My application needs exclusive control of hardware channels"
179 is being used to support device-to-memory operations. A channel that is
204 not be used by the general-purpose allocator. It can be set at
211 considered by the general-purpose allocator even after a call to