On Tue, Feb 27, 2018 at 03:08:58PM +0100, Stephan Müller wrote:
> Am Freitag, 23. Februar 2018, 13:00:26 CET schrieb Herbert Xu:
>
> Hi Herbert,
>
> > On Fri, Feb 23, 2018 at 09:33:33AM +0100, Stephan Müller wrote:
> > > A simple copy operation, however, will imply that in one AIO recvmsg
> > >
On Tue, 27 Feb 2018 15:08:58 +0100
Stephan Müller wrote:
> Am Freitag, 23. Februar 2018, 13:00:26 CET schrieb Herbert Xu:
>
> Hi Herbert,
Hi Stephan / Herbert,
>
> > On Fri, Feb 23, 2018 at 09:33:33AM +0100, Stephan Müller wrote:
> > > A simple copy operation, however,
Am Freitag, 23. Februar 2018, 13:00:26 CET schrieb Herbert Xu:
Hi Herbert,
> On Fri, Feb 23, 2018 at 09:33:33AM +0100, Stephan Müller wrote:
> > A simple copy operation, however, will imply that in one AIO recvmsg
> > request, only *one* IOCB can be set and processed.
>
> Sure, but the recvmsg
On Fri, Feb 23, 2018 at 09:33:33AM +0100, Stephan Müller wrote:
>
> A simple copy operation, however, will imply that in one AIO recvmsg request,
> only *one* IOCB can be set and processed.
Sure, but the recvmsg will return as soon as the crypto API encrypt
or decrypt function returns. It's
Am Donnerstag, 22. Februar 2018, 14:06:00 CET schrieb Herbert Xu:
Hi Herbert,
> On Fri, Feb 09, 2018 at 11:02:27PM +0100, Stephan Müller wrote:
> > Hi,
> >
> > Herbert, the patch 1 is meant for stable. However, this patch as is
> > only applies to the new AF_ALG interface implementation.
On Fri, Feb 09, 2018 at 11:02:27PM +0100, Stephan Müller wrote:
> Hi,
>
> Herbert, the patch 1 is meant for stable. However, this patch as is
> only applies to the new AF_ALG interface implementation. Though,
> the issue goes back to the first implementation of AIO support.
> Shall I try prepare
Hi,
Herbert, the patch 1 is meant for stable. However, this patch as is
only applies to the new AF_ALG interface implementation. Though,
the issue goes back to the first implementation of AIO support.
Shall I try prepare a patch for the old AF_ALG implementation
as well?
Changes from v2:
*