linux-kernel - dmaengine: the purpouse of dma_async_tx

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <20090622174501.5187e750@dragos-tp.localdomain>
Date:	Mon, 22 Jun 2009 17:45:01 +0300
From:	Dragos Tatulea <dtatulea@...acom.com>
To:	linux-kernel@...r.kernel.org
Cc:	Octavian Purdila <opurdila@...acom.com>,
	Dragos Tatulea <dtatulea@...acom.com>
Subject: dmaengine: the purpouse of dma_async_tx_callback

Hi,

	What is the purpouse of dma_async_tx_callback from
	dma_async_tx_descriptor in the dma engine api context? It can be called
	only from the engine side and I can't see the point in that.

	At a first glance it looks like a way of notifying the dma clients of
	the descriptor completion, but on closer inspection dma clients don't
	have access to the dma_async_tx_descriptor structure, they only have
	the cookie. It would be really useful to notify clients of operation
	completion via this callback and I'd gladly provide a patch for that.

Thanks,
Dragos
--
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/