On 2015-05-28 14:26, Gordan Bobic wrote:
On 2015-05-28 13:12, Nikos Mavrogiannopoulos wrote:
On Thu, May 28, 2015 at 12:06 PM, Gordan Bobic
wrote:
Does that mean it is not a 0-copy related problem?
In fact, I can confirm the problem is not at all related to mv_cesa.
I just unloaded the mv_ces
On 2015-05-28 13:12, Nikos Mavrogiannopoulos wrote:
On Thu, May 28, 2015 at 12:06 PM, Gordan Bobic
wrote:
Does that mean it is not a 0-copy related problem?
In fact, I can confirm the problem is not at all related to mv_cesa.
I just unloaded the mv_cesa driver which means that with cryptodev
i
On Thu, May 28, 2015 at 12:06 PM, Gordan Bobic wrote:
>> Does that mean it is not a 0-copy related problem?
> In fact, I can confirm the problem is not at all related to mv_cesa.
> I just unloaded the mv_cesa driver which means that with cryptodev
> it will be the kernel doing the AES using the ge
On 2015-05-28 11:00, Gordan Bobic wrote:
On 2015-05-27 23:33, Phil Sutter wrote:
On Wed, May 27, 2015 at 10:36:29PM +0100, Gordan Bobic wrote:
What do I need to change in which file to disable 0-copy?
Have a look at main.c, line 239:
| if (cop->flags & COP_FLAG_NO_ZC)
| ret = __crypt
On 2015-05-27 23:33, Phil Sutter wrote:
On Wed, May 27, 2015 at 10:36:29PM +0100, Gordan Bobic wrote:
What do I need to change in which file to disable 0-copy?
Have a look at main.c, line 239:
| if (cop->flags & COP_FLAG_NO_ZC)
| ret = __crypto_run_std(ses_ptr, &kcop->cop);
| else
|
