On Sat, Mar 14, 2015 at 1:16 PM, Horia Geantă <[email protected]> wrote: > On 3/13/2015 8:37 PM, Tom Lendacky wrote: >>> + >>> + /* Try to backlog request (if allowed) */ >>> + return crypto_enqueue_request(&priv->chan[ch].queue, areq); >> >> I'd remembered something about how hardware drivers should use their >> own list element for queuing, searched back and found this: >> >> http://marc.info/?l=linux-crypto-vger&m=137609769605139&w=2 > > The crypto_async_request "list" field is used only for queuing using the > crypto API functions - crypto_{enqueue,dequeue}_request. > > I am not sure I understand what is the problem. > Are crypto_{enqueue,dequeue}_request part of *internal* crypto API?
I don't believe that the enqueue/dequeue functions are internal API. I based my code on the usage of other hardware offload drivers. Their use is somewhat different because most of the other hardware can only handle a single request at a time. mh -- Martin Hicks P.Eng. | [email protected] Bork Consulting Inc. | +1 (613) 266-2296 -- To unsubscribe from this list: send the line "unsubscribe linux-crypto" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
