Re: [Cryptodev-linux-devel] [PATCH] RFC: third working version of the async ops

2010-10-20 Thread Phil Sutter
Hey, On Wed, Oct 20, 2010 at 12:35:51PM +0200, Nikos Mavrogiannopoulos wrote: > On Wed, Oct 13, 2010 at 5:17 PM, Phil Sutter wrote: > > Still ugly as hell (and therefore TODO): > > - having to pass task_struct and mm_struct from the calling process > >  around > > - need to copy the IV right at w

Re: [Cryptodev-linux-devel] [PATCH] RFC: third working version of the async ops

2010-10-20 Thread Nikos Mavrogiannopoulos
On Wed, Oct 13, 2010 at 5:17 PM, Phil Sutter wrote: > Still ugly as hell (and therefore TODO): > - having to pass task_struct and mm_struct from the calling process >  around > - need to copy the IV right at write() time (copy_from_user seems to >  work in process context only) I'm still trying t

Re: [Cryptodev-linux-devel] [PATCH] RFC: third working version of the async ops

2010-10-13 Thread Phil Sutter
Hello Nikos, On Wed, Oct 13, 2010 at 05:52:57PM +0200, Nikos Mavrogiannopoulos wrote: > On 10/13/2010 05:17 PM, Phil Sutter wrote: > > Still ugly as hell (and therefore TODO): > > - having to pass task_struct and mm_struct from the calling process > > around > > - need to copy the IV right at wr

[Cryptodev-linux-devel] [PATCH] RFC: third working version of the async ops

2010-10-13 Thread Phil Sutter
Changes since second version: - use an own workqueue per open file in order to retain system interactivity. - Have a variable list of items in the job queue (increasing one by one until some arbitrary upper limit). - Locking fixup: synchronising on the list items only is not possible. Instead