All of lore.kernel.org
 help / color / mirror / Atom feed
From: Roberto Suarez Soto <robe@allenta.com>
To: netdev@vger.kernel.org
Subject: High ksoftirq CPU load, high latency, __xfrm4_find_bundle likely culprit?
Date: Mon, 12 Mar 2012 16:50:35 +0100	[thread overview]
Message-ID: <4F5E1B4B.2070807@allenta.com> (raw)

Hi,

	we've got a load problem in one of our IPSec gateways, running openswan 
1:2.6.28+dfsg-5+squeeze1 and kernel 2.6.32-5-686-bigmem (Debian Squeeze). The 
symptoms are:

	- High ksoftirqd load
	- High network latency (pings up to 200ms in the same switch)
	- At those times, "perf top" shows a high CPU usage for syscalls 
__xfrm4_find_bundle, des3_ede_decrypt and des3_ede_encrypt

	We've already discarded NIC problems, and traffic is not so high as to 
justify these problems. In particular, we have a bond0 for the two NICs that 
deal with LAN traffic, and when the problem appears the stats are quite tame: 
3k-4k packets per second, 3MBytes/s.

	We're migrating away from 3DES to mitigate this problem, but the real culprit 
seems to be __xfrm4_find_bundle. Is there something wrong? Is it a bug, or 
something that we've not tuned properly?

	Thanks,

-- 
         Roberto Suarez Soto                             Allenta Consulting
         robe@allenta.com                                   www.allenta.com
                                                            +34 881 922 600

Este correo electrónico contiene información estrictamente confidencial y
es de uso exclusivo del destinatario, quedando prohibida a cualquier otra
persona su revelación, copia, distribución, o el ejercicio de cualquier
acción relativa a su contenido. Si ha recibido este mensaje por error, por
favor conteste a su remitente mediante correo electrónico y proceda a
borrarlo de su sistema. Rogamos nos comunique inmediatamente sobre
cualquier inconveniente que pueda tener usted en relación al envío de este
tipo de correo electrónico.

Sus datos personales serán tratados de forma confidencial y no serán
cedidos a terceros ajenos a ALLENTA CONSULTING, S.L. En cualquier caso,
podrá ejercer los derecho de oposición, acceso, rectificación y cancelación
de acuerdo con lo establecido en la Ley Orgánica 15/99, de 13 de diciembre,
de Protección de Datos de Carácter Personal dirigiéndose a ALLENTA
CONSULTING, S.L. en C/Enrique Mariñas 36, 2º piso, oficina 8, 15009 – A
Coruña  o en la dirección de electrónico info@allenta.com

             reply	other threads:[~2012-03-12 15:57 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-12 15:50 Roberto Suarez Soto [this message]
2012-03-12 19:51 ` High ksoftirq CPU load, high latency, __xfrm4_find_bundle likely culprit? David Miller

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4F5E1B4B.2070807@allenta.com \
    --to=robe@allenta.com \
    --cc=netdev@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.