blob: 9f59fcbf5d82b9ce3236dd044f9e1d75b4600e79 [file] [log] [blame]
Dan Williamsc5d2b9f2007-09-20 15:49:08 -07001 Asynchronous Transfers/Transforms API
2
31 INTRODUCTION
4
52 GENEALOGY
6
73 USAGE
83.1 General format of the API
93.2 Supported operations
103.3 Descriptor management
113.4 When does the operation execute?
123.5 When does the operation complete?
133.6 Constraints
143.7 Example
15
Dan Williams28405d82009-01-05 17:14:31 -0700164 DMAENGINE DRIVER DEVELOPER NOTES
Dan Williamsc5d2b9f2007-09-20 15:49:08 -0700174.1 Conformance points
Dan Williams28405d82009-01-05 17:14:31 -0700184.2 "My application needs exclusive control of hardware channels"
Dan Williamsc5d2b9f2007-09-20 15:49:08 -070019
205 SOURCE
21
22---
23
241 INTRODUCTION
25
26The async_tx API provides methods for describing a chain of asynchronous
27bulk memory transfers/transforms with support for inter-transactional
28dependencies. It is implemented as a dmaengine client that smooths over
29the details of different hardware offload engine implementations. Code
30that is written to the API can optimize for asynchronous operation and
31the API will fit the chain of operations to the available offload
32resources.
33
342 GENEALOGY
35
36The API was initially designed to offload the memory copy and
37xor-parity-calculations of the md-raid5 driver using the offload engines
38present in the Intel(R) Xscale series of I/O processors. It also built
39on the 'dmaengine' layer developed for offloading memory copies in the
40network stack using Intel(R) I/OAT engines. The following design
41features surfaced as a result:
421/ implicit synchronous path: users of the API do not need to know if
43 the platform they are running on has offload capabilities. The
44 operation will be offloaded when an engine is available and carried out
45 in software otherwise.
462/ cross channel dependency chains: the API allows a chain of dependent
47 operations to be submitted, like xor->copy->xor in the raid5 case. The
48 API automatically handles cases where the transition from one operation
49 to another implies a hardware channel switch.
503/ dmaengine extensions to support multiple clients and operation types
51 beyond 'memcpy'
52
533 USAGE
54
553.1 General format of the API:
56struct dma_async_tx_descriptor *
57async_<operation>(<op specific parameters>,
58 enum async_tx_flags flags,
59 struct dma_async_tx_descriptor *dependency,
60 dma_async_tx_callback callback_routine,
61 void *callback_parameter);
62
633.2 Supported operations:
64memcpy - memory copy between a source and a destination buffer
65memset - fill a destination buffer with a byte value
66xor - xor a series of source buffers and write the result to a
67 destination buffer
68xor_zero_sum - xor a series of source buffers and set a flag if the
69 result is zero. The implementation attempts to prevent
70 writes to memory
71
723.3 Descriptor management:
73The return value is non-NULL and points to a 'descriptor' when the operation
74has been queued to execute asynchronously. Descriptors are recycled
75resources, under control of the offload engine driver, to be reused as
76operations complete. When an application needs to submit a chain of
77operations it must guarantee that the descriptor is not automatically recycled
78before the dependency is submitted. This requires that all descriptors be
79acknowledged by the application before the offload engine driver is allowed to
80recycle (or free) the descriptor. A descriptor can be acked by one of the
81following methods:
821/ setting the ASYNC_TX_ACK flag if no child operations are to be submitted
832/ setting the ASYNC_TX_DEP_ACK flag to acknowledge the parent
84 descriptor of a new operation.
853/ calling async_tx_ack() on the descriptor.
86
873.4 When does the operation execute?
88Operations do not immediately issue after return from the
89async_<operation> call. Offload engine drivers batch operations to
90improve performance by reducing the number of mmio cycles needed to
91manage the channel. Once a driver-specific threshold is met the driver
92automatically issues pending operations. An application can force this
93event by calling async_tx_issue_pending_all(). This operates on all
94channels since the application has no knowledge of channel to operation
95mapping.
96
973.5 When does the operation complete?
98There are two methods for an application to learn about the completion
99of an operation.
1001/ Call dma_wait_for_async_tx(). This call causes the CPU to spin while
101 it polls for the completion of the operation. It handles dependency
102 chains and issuing pending operations.
1032/ Specify a completion callback. The callback routine runs in tasklet
104 context if the offload engine driver supports interrupts, or it is
105 called in application context if the operation is carried out
106 synchronously in software. The callback can be set in the call to
107 async_<operation>, or when the application needs to submit a chain of
108 unknown length it can use the async_trigger_callback() routine to set a
109 completion interrupt/callback at the end of the chain.
110
1113.6 Constraints:
1121/ Calls to async_<operation> are not permitted in IRQ context. Other
113 contexts are permitted provided constraint #2 is not violated.
1142/ Completion callback routines cannot submit new operations. This
115 results in recursion in the synchronous case and spin_locks being
116 acquired twice in the asynchronous case.
117
1183.7 Example:
119Perform a xor->copy->xor operation where each operation depends on the
120result from the previous operation:
121
122void complete_xor_copy_xor(void *param)
123{
124 printk("complete\n");
125}
126
127int run_xor_copy_xor(struct page **xor_srcs,
128 int xor_src_cnt,
129 struct page *xor_dest,
130 size_t xor_len,
131 struct page *copy_src,
132 struct page *copy_dest,
133 size_t copy_len)
134{
135 struct dma_async_tx_descriptor *tx;
136
137 tx = async_xor(xor_dest, xor_srcs, 0, xor_src_cnt, xor_len,
138 ASYNC_TX_XOR_DROP_DST, NULL, NULL, NULL);
139 tx = async_memcpy(copy_dest, copy_src, 0, 0, copy_len,
140 ASYNC_TX_DEP_ACK, tx, NULL, NULL);
141 tx = async_xor(xor_dest, xor_srcs, 0, xor_src_cnt, xor_len,
142 ASYNC_TX_XOR_DROP_DST | ASYNC_TX_DEP_ACK | ASYNC_TX_ACK,
143 tx, complete_xor_copy_xor, NULL);
144
145 async_tx_issue_pending_all();
146}
147
148See include/linux/async_tx.h for more information on the flags. See the
149ops_run_* and ops_complete_* routines in drivers/md/raid5.c for more
150implementation examples.
151
1524 DRIVER DEVELOPMENT NOTES
Dan Williams28405d82009-01-05 17:14:31 -0700153
Dan Williamsc5d2b9f2007-09-20 15:49:08 -07001544.1 Conformance points:
155There are a few conformance points required in dmaengine drivers to
156accommodate assumptions made by applications using the async_tx API:
1571/ Completion callbacks are expected to happen in tasklet context
1582/ dma_async_tx_descriptor fields are never manipulated in IRQ context
1593/ Use async_tx_run_dependencies() in the descriptor clean up path to
160 handle submission of dependent operations
161
Dan Williams28405d82009-01-05 17:14:31 -07001624.2 "My application needs exclusive control of hardware channels"
163Primarily this requirement arises from cases where a DMA engine driver
164is being used to support device-to-memory operations. A channel that is
165performing these operations cannot, for many platform specific reasons,
166be shared. For these cases the dma_request_channel() interface is
167provided.
Dan Williamsc5d2b9f2007-09-20 15:49:08 -0700168
Dan Williams28405d82009-01-05 17:14:31 -0700169The interface is:
170struct dma_chan *dma_request_channel(dma_cap_mask_t mask,
171 dma_filter_fn filter_fn,
172 void *filter_param);
Dan Williamsc5d2b9f2007-09-20 15:49:08 -0700173
Dan Williams28405d82009-01-05 17:14:31 -0700174Where dma_filter_fn is defined as:
175typedef bool (*dma_filter_fn)(struct dma_chan *chan, void *filter_param);
Dan Williamsc5d2b9f2007-09-20 15:49:08 -0700176
Dan Williams28405d82009-01-05 17:14:31 -0700177When the optional 'filter_fn' parameter is set to NULL
178dma_request_channel simply returns the first channel that satisfies the
179capability mask. Otherwise, when the mask parameter is insufficient for
180specifying the necessary channel, the filter_fn routine can be used to
181disposition the available channels in the system. The filter_fn routine
182is called once for each free channel in the system. Upon seeing a
183suitable channel filter_fn returns DMA_ACK which flags that channel to
184be the return value from dma_request_channel. A channel allocated via
185this interface is exclusive to the caller, until dma_release_channel()
186is called.
Dan Williamsc5d2b9f2007-09-20 15:49:08 -0700187
Dan Williams28405d82009-01-05 17:14:31 -0700188The DMA_PRIVATE capability flag is used to tag dma devices that should
189not be used by the general-purpose allocator. It can be set at
190initialization time if it is known that a channel will always be
191private. Alternatively, it is set when dma_request_channel() finds an
192unused "public" channel.
Dan Williamsc5d2b9f2007-09-20 15:49:08 -0700193
Dan Williams28405d82009-01-05 17:14:31 -0700194A couple caveats to note when implementing a driver and consumer:
1951/ Once a channel has been privately allocated it will no longer be
196 considered by the general-purpose allocator even after a call to
197 dma_release_channel().
1982/ Since capabilities are specified at the device level a dma_device
199 with multiple channels will either have all channels public, or all
200 channels private.
Dan Williamsc5d2b9f2007-09-20 15:49:08 -0700201
2025 SOURCE
Dan Williams28405d82009-01-05 17:14:31 -0700203
204include/linux/dmaengine.h: core header file for DMA drivers and api users
Dan Williamsc5d2b9f2007-09-20 15:49:08 -0700205drivers/dma/dmaengine.c: offload engine channel management routines
206drivers/dma/: location for offload engine drivers
207include/linux/async_tx.h: core header file for the async_tx api
208crypto/async_tx/async_tx.c: async_tx interface to dmaengine and common code
209crypto/async_tx/async_memcpy.c: copy offload
210crypto/async_tx/async_memset.c: memory fill offload
211crypto/async_tx/async_xor.c: xor and xor zero sum offload