On 11/12/2014 04:51 PM, Herbert Xu wrote:
On Wed, Nov 12, 2014 at 09:41:38AM +0100, Steffen Klassert wrote:
Can't we just use cryptd unconditionally to fix this reordering problem?
I think the idea is that most of the time cryptd isn't required
so we want to stick with direct processing to lower latency.
I think the simplest fix would be to punt to cryptd as long as
there are cryptd requests queued.
I've tried that method when I started to think about the fix, but it
will cause 2 other issues per test while resolving the reordering one,
as follows:
1 The work queue can not handle so many packets when the traffic is very
high(over 200M/S), and it would drop most of them when the queue length
is beyond CRYPTD_MAX_CPU_QLEN.
2 Soft lockups are observed, per my analysis, the cause is: in some
extreme cases, all packets would be sent to the cryptd once there are
requests already in it, this will let the net poll functions return
pretty fast, and lead too many hw interrupts triggered in a certain period.
//Ming Liu
Cheers,
--
To unsubscribe from this list: send the line "unsubscribe linux-crypto" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
