On 04/05/2011, at 3:53 AM, Mike Belopuhov wrote:
> hi,
>
> recently me and jsg have figured out that a traffic burst can kill
> your interface (deplete the rx ring) if you're using ipsec. the
> problem is that there's no limit on number of outstanding crypto
> operations. every job contains a po
On Tue, May 3, 2011 at 9:24 PM, Claudio Jeker
wrote:
> On Tue, May 03, 2011 at 07:53:56PM +0200, Mike Belopuhov wrote:
>> hi,
>>
>> recently me and jsg have figured out that a traffic burst can kill
>> your interface (deplete the rx ring) if you're using ipsec. the
>> problem is that there's no l
On Tue, May 03, 2011 at 07:53:56PM +0200, Mike Belopuhov wrote:
> hi,
>
> recently me and jsg have figured out that a traffic burst can kill
> your interface (deplete the rx ring) if you're using ipsec. the
> problem is that there's no limit on number of outstanding crypto
> operations. every jo
hi,
recently me and jsg have figured out that a traffic burst can kill
your interface (deplete the rx ring) if you're using ipsec. the
problem is that there's no limit on number of outstanding crypto
operations. every job contains a pointer to a cluster that comes
from the nic driver.
under hig
