All of lore.kernel.org
 help / color / mirror / Atom feed
From: Roberto Suarez Soto <robe@allenta.com>
To: netfilter@vger.kernel.org
Subject: Re: High ksoftirqd CPU load, high latency [somewhat SOLVED]
Date: Mon, 12 Mar 2012 10:30:56 +0100	[thread overview]
Message-ID: <4F5DC250.6060108@allenta.com> (raw)
In-Reply-To: <4F50981E.8020107@allenta.com>

Hi,

	I think I have this nailed down, and it happens not to be related to iptables 
at all. My fault: one of the main jobs of the problematic boxes is being IPSec 
gateways, which I shamefully forgot to say when reporting this problem. And it 
seems this is the problem.

	Using "perf top", I can see that when ksoftirq is at 100% CPU the syscalls 
being called are __xfrm4_find_bundle (occupying most of the CPU), 
des3_ede_encrypt and des3_ede_decrypt. Last friday I thought the problem were 
just the latter two, and after some googling and finding that 3DES is actually 
more inefficient than AES, I started to change 3DES for AES-128. But today 
it's clear that, though 3DES may be a part of the problem, the gist of it is 
__xfrm4_find_bundle.

	I've been searching for some explanation about what this syscall does, and 
found a message in a forum 
(http://www.linuxforums.org/forum/kernel/184652-high-softirq-cpu-usage-while-ipsec-active.html) 
hinting to xfrm settings as the culprit. But anyway, I'm going to ask in 
openswan's list, which seems the proper place to do it.

	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


  parent reply	other threads:[~2012-03-12  9:30 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-02  9:51 High ksoftirqd CPU load, high latency Roberto Suarez Soto
2012-03-02 11:52 ` Kerin Millar
2012-03-02 12:03   ` Jan Engelhardt
2012-03-02 12:20   ` Roberto Suarez Soto
2012-03-12  9:30 ` Roberto Suarez Soto [this message]
2012-05-18 14:51   ` High ksoftirqd CPU load, high latency [somewhat SOLVED] Vairavan

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=4F5DC250.6060108@allenta.com \
    --to=robe@allenta.com \
    --cc=netfilter@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.