it means they dont have much more done yet than you do if you have Crypto to a useable state then all that need be done is us in in Async mode ~ though most get it backwards on how to go about it - nasty place to fail but it is remarkably simple once one gets the hang of it = you do new on whatever you have in a runnable with synchronized keyword on every storage class being very very careful to really really understand how synchronization works
it is very cheap to use in source code ( like free ) costs near- nothing in run-time and resolves on viewing the code as an execution path that something is going to follow ~ some coders use the notion of "Sparky The Dog" going through the code so you set it up so that only one Sparky can be in any code block at any time - you can run thousands of threads and not load even these seemingly small devices if the code is written correctly make the code a runnable and call new on each and put synchronized keyword everywhere and load test it till it fails commercial servers on heavier equipment should be able to take momentary spikes of 10,000 requests like it is routine activity and keep everything sorted out all async means is that the launching thread does not have to go in to the code that drives the object ~ they have it all over the Android code-base as interfaces + that is a good design which you can model your code to if it is synchronized correctly On Nov 3, 6:53 am, tilak <tangudu.ti...@gmail.com> wrote: > Hi Crypto friends > > 1)I see in kernel sources- gingerbread/kernel/crypto/cryptd.c, > Asynchronous Crypto API interface is developed for both Block Cipher > and Hash Algorithms. > > But in the "TO DO List" mentioned in the > linkhttp://gondor.apana.org.au/~herbert/crypto/ > ,I see "Asynchronous hash support." need to be implemented > (and not yet implemented.) > > Could you please clarify, whether Asynchronous crypto API interface is > developed for both Block Cipher and Hash Algorithms or not? > > 2)Our requirement is Asynchronous Crypto API interface for our > Hardware crypto device( designed by us) > > I see the below quotes in the link "http://www.mjmwired.net/kernel/ > Documentation/crypto/api-intro.txt > > 47 Support for hardware crypto devices via an asynchronous interface > is > 48 under development. > > I apologize,What does the above quotes mean? > > Do current Asynchronous Crypto API interface do not support hardware > crypto devices ? > > Thanks in advance -- unsubscribe: android-kernel+unsubscr...@googlegroups.com website: http://groups.google.com/group/android-kernel
