Lines Matching +full:engine +full:- +full:specific

1 .. SPDX-License-Identifier: GPL-2.0
32 bulk memory transfers/transforms with support for inter-transactional
34 the details of different hardware offload engine implementations.  Code
43 xor-parity-calculations of the md-raid5 driver using the offload engines
51    operation will be offloaded when an engine is available and carried out
54    operations to be submitted, like xor->copy->xor in the raid5 case.  The
64 -----------------------------
69   async_<operation>(<op specific parameters>, struct async_submit_ctl *submit)
72 ------------------------
92 -------------------------
94 The return value is non-NULL and points to a 'descriptor' when the operation
96 resources, under control of the offload engine driver, to be reused as
100 acknowledged by the application before the offload engine driver is allowed to
110 ------------------------------------
113 async_<operation> call.  Offload engine drivers batch operations to
115 manage the channel.  Once a driver-specific threshold is met the driver
122 -------------------------------------
131    context if the offload engine driver supports interrupts, or it is
139 ---------------
148 -----------
150 Perform a xor->copy->xor operation where each operation depends on the
178 	    submit->depend_tx = tx;
199 ----------------------
210 -----------------------------------------------------------------
212 Primarily this requirement arises from cases where a DMA engine driver
213 is being used to support device-to-memory operations.  A channel that is
214 performing these operations cannot, for many platform specific reasons,
240 not be used by the general-purpose allocator.  It can be set at
248    considered by the general-purpose allocator even after a call to
255 ---------
260     offload engine channel management routines
262     location for offload engine drivers