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: Mon, 11 Sep 2006 23:18:59 -0700 From: "Dan Williams" <dan.j.williams@...il.com> To: "Roland Dreier" <rdreier@...co.com> Cc: "Jeff Garzik" <jeff@...zik.org>, neilb@...e.de, linux-raid@...r.kernel.org, akpm@...l.org, linux-kernel@...r.kernel.org, christopher.leech@...el.com, "Evgeniy Polyakov" <johnpol@....mipt.ru> Subject: Re: [PATCH 08/19] dmaengine: enable multiple clients and operations On 9/11/06, Roland Dreier <rdreier@...co.com> wrote: > Jeff> Are we really going to add a set of hooks for each DMA > Jeff> engine whizbang feature? ...ok, but at some level we are going to need a file that has: EXPORT_SYMBOL_GPL(dma_whizbang_op1) . . . EXPORT_SYMBOL_GPL(dma_whizbang_opX) correct? > Dan> What's the alternative? But, also see patch 9 "dmaengine: > Dan> reduce backend address permutations" it relieves some of this > Dan> pain. > > I guess you can pass an opcode into a common "start operation" function. But then we still have the problem of being able to request a memory copy operation of a channel that only understands xor, a la Jeff's comment to patch 12: "Further illustration of how this API growth is going wrong. You should create an API such that it is impossible for an XOR transform to ever call non-XOR-transform hooks." > With all the memcpy / xor / crypto / etc. hardware out there already, > we definitely have to get this interface right. > > - R. I understand what you are saying Jeff, the implementation can be made better, but something I think is valuable is the ability to write clients once like NET_DMA and RAID5_DMA and have them run without modification on any platform that can provide the engine interface rather than needing a client per architecture IOP_RAID5_DMA...FOO_X_RAID5_DMA. Or is this an example of the where "Do What You Must, And No More" comes in, i.e. don't worry about making a generic RAID5_DMA while there is only one implementation existence? I also want to pose the question of whether the dmaengine interface should handle cryptographic transforms? We already have Acrypto: http://tservice.net.ru/~s0mbre/blog/devel/acrypto/index.html. At the same time since IOPs can do Galois Field multiplication and XOR it would be nice to take advantage of that for crypto acceleration, but this does not fit the model of a device that Acrypto supports. 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