| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Date: Wed, 11 Jul 2007 09:56:31 -0700 From: "Dan Williams" <dan.j.williams@...el.com> To: "Zhang Wei-r63237" <Wei.Zhang@...escale.com> Cc: akpm@...ux-foundation.org, paulus@...ba.org, galak@...nel.crashing.org, linuxppc-dev@...abs.org, linux-kernel@...r.kernel.org, shannon.nelson@...el.com Subject: Re: [PATCH 3/4] Extend the DMA-engine API. On 7/11/07, Zhang Wei-r63237 <Wei.Zhang@...escale.com> wrote: > Hi, Dan, > > Do you mention here: http://marc.info/?l=linux-raid&m=118290909614463&w=2 ? > I see the async_tx is located at crypto/ of the above page, but my patch is for DMA engine in drivers/dma and for DMA engine driver. > > Thanks! > Wei. Hi Wei, I was referring to: http://marc.info/?l=linux-raid&m=118290909528910&w=2 async_tx is an api that exploits the raw capabilities of the new dmaengine interface. For your case when the existing api calls do not provide the proper interface you can open code something like the following: tx = dev->device_prep_dma_<operation>(chan, len, int_flag) tx->tx_set_src(dma_addr_t, tx, index /* for multi-source ops */) tx->tx_set_dest(dma_addr_t, tx, index) tx->tx_submit(tx) The expectation is that the most common usages of dmaengines will use async_tx calls, or the 'dma_async_memcpy_foo_to_bar' helper routines. -- Dan - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists